researchforge-autorun SKILL.md skillA
researchforge-autorun from forger-labs-hq/researchforge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add forger-labs-hq/researchforge/researchforge-autorun@git:20261115.6378c2bPins git:20261115.6378c2b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- forger-labs-hq/researchforge
- Path
src/researchforge/claude/skills/researchforge-autorun/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261115.6378c2b, committed Nov 15, 2026
- First version recorded
- Sep 2, 2026
- Size
- 4,902 bytes
- Repository stars
- 9
- License
- Apache-2.0
Drive the autonomous research loop round after round — ask the engine which node to expand, plan there, run, read the result, repeat. Use when the user wants to keep improving a repository over many rounds, or wants autorun without an AI API key.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Drive the research loop `researchforge autorun` runs this loop by itself when an API key is configured. Without one, **you** are the intelligence and the engine is still the lab: it chooses where to search, validates what you write, runs the benchmark, and records the result. Your job is the one part it cannot do without a provider — writing the plan and the patches. Never guess at the next move. The engine's search knows things a results table does not show: which ideas were already tried at which node, what is in each node's ancestry, and how much budget is left. ## 1. Ask where to go next ```bash researchforge autorun --dry-run --json ``` This spends nothing — no AI call, no experiment runs. It returns the node the loop would expand, the hypotheses it would try there in ranked order, and the exact command to take that step: - `recommended_node` — the experiment to build on, or `baseline`; - `next_command` — run this next; - `merge_opportunities` — if set, THIS IS THE HIGHEST PRIORITY MOVE; - `dag_state` — total, improved, baseline, current best. (Kaggle competitions use the `/overnight` skill and `researchforge kaggle prepare-round`, not this loop.) …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_bhknalihz3in33hk/184b8e4aed419487931416774660a696c36c06a2ce90f336c86f7da660245de3.json
Then /plugin install researchforge-autorun@markdownregistry-bhknalihz3in33hk in Claude Code. It installs git:20261115.6378c2b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add forger-labs-hq/researchforge/researchforge-autorun@sha256:184b8e4aed419487The line at the top of this page pins the label git:20261115.6378c2b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bhknalihz3in33hk)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in forger-labs-hq/researchforge/researchforge-autorun since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of researchforge-autorun from somewhere else? Ask it: where did my researchforge-autorun come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Sep 2, 2026 and Nov 15, 2026, about one every 74 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261115.6378c2b latest | 2026-11-15 | 6378c2b | 4,902 B | A | view · diff |
| git:20260902.20c768e | 2026-09-02 | 20c768e | 4,203 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/researchforge-autorun/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4902 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
forger-labs-hq/researchforge · 9 stars · license Apache-2.0 · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bhknalihz3in33hk GET https://markdownregistry.com/api/v1/resolve?ref=forger-labs-hq/researchforge/researchforge-autorun GET https://markdownregistry.com/api/v1/blob/184b8e4aed419487931416774660a696c36c06a2ce90f336c86f7da660245de3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.