Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add radimsem/forge-skills --skill blacksmith-orchestrategit clone --depth 1 https://github.com/radimsem/forge-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/radimsem/forge-skills/blacksmith-orchestrate)<a href="https://agentmods.dev/skills/radimsem/forge-skills/blacksmith-orchestrate"><img src="https://agentmods.dev/badge/skills/radimsem/forge-skills/blacksmith-orchestrate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/radimsem/forge-skills/blacksmith-orchestrate"><img src="https://agentmods.dev/badge/skills/radimsem/forge-skills/blacksmith-orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00079 | $0.05267 |
| Opus 5.5 | $0.00032 | $0.02107 |
| Sonnet 5.5 | $0.00016 | $0.01053 |
| Haiku 4.5 | $0.00008 | $0.00527 |
Grade A, and why
blacksmith-orchestrate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blacksmith Orchestrate
Schedule related tasks across worktrees, then dispatch one forge run per task.
Overview
Each dispatched task runs forge's twelve-step workflow. This skill decides which tasks can run together, what model and review depth each needs, and which worktree holds its changes.
Nine numbered steps, split by one gate, deliberately mirroring forge's shape:
Part 1 — Plan (1–5): normalize → materialize → analyze → schedule → [GATE] battle plan
Part 2 — Execute (6–9): provision → dispatch waves → relay → close-out
gate held: no worktree is created and no forge Part 2 runs until "yes, forge them"
| Step | Action |
|---|---|
| 1 | Parse the invocation; split orchestrator flags from pass-through forge flags; route the work source into a canonical task list |
| 2 | Materialize refs: spec-file and free-form routes get real issue refs via /to-tickets, or synthetic T1..Tn IDs if the user declines filing |
| 3 | Analyze: route each task to the plan-sourced path or the scout fan-out |
| 4 | Build the collision graph, triage matrix and worktree grouping, then scheduling waves |
| 5 | [GATE] one battle plan, one approval |
| 6 | Provision worktrees; write the run ledger |
| 7 | Dispatch waves: one agent per task at its assigned model tier and forge depth |
| 8 | Relay: prove a blocker's changes are on the dependent's base, rebase, release |
| 9 | Close-out: aggregate report, PR list, worktree cleanup reminders, self-evolution |
Every dispatched run must verify its Step 12 /goal before preparing a commit. No run writes back to its source issue or ticket, even with afk. Step 2 may file new issues through /to-tickets for plan and free-form routes, including under automode; forge Step 10 may likewise file spin-off issues. See references/entry-routes.md.
The Step 5 "yes, forge them" approval also selects commit and PR creation for every task named in the approved battle plan (see Step 7). With automode alone, no one makes that selection, so dispatched runs stop with a plan at Step 12 and push nothing. afk is the single sanctioned exception: it authorizes unattended commits, PRs, and blocking-PR merges. Terminal PRs and worktree cleanup remain with the user under every flag combination.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/afk.md 5.8 KB
- references/anti-patterns.md 1.7 KB
- references/battle-plan.md 6.1 KB
- references/collision-graph.md 12 KB
- references/entry-routes.md 11 KB
- references/flags.md 6.3 KB
- references/ledger.md 11 KB
- references/plan-sourced.md 9.5 KB
- references/relay.md 5.8 KB
- references/scheduling.md 6.7 KB
- references/triage.md 7.2 KB
- scripts/scout-fanout.mjs 2.6 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +2 lines 7795216418a4
- 1mo ago First seen · 167 lines · 79 tokens per session scan A 33b019a601c4
blacksmith-orchestrate is a skill published in the GitHub repository radimsem/forge-skills (15 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 5,267 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.