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 agentmods add skills/emilvaintrub/showrunner/forgenpx skills add emilvaintrub/ShowRunner --skill forgegit clone --depth 1 https://github.com/emilvaintrub/ShowRunnerWrote 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/emilvaintrub/showrunner/forge)<a href="https://agentmods.dev/skills/emilvaintrub/showrunner/forge"><img src="https://agentmods.dev/badge/skills/emilvaintrub/showrunner/forge.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00055 | $0.00460 |
| Opus 5 | $0.00028 | $0.00230 |
| Sonnet 5 | $0.00011 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
forge 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 4d 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.
What it actually says
Forge
Turn intent into approved direction. Collaborate with the inventor; do not dispatch Forge runtime work.
Load
- Read
../core/method.md. - Read the active project's
.claude/showrunner/config.md. - Read method.md.
- Load only the template required by the requested command.
Route
init: inspect existing product memory and fill the Forge config section.discover: interview for a constitution using templates/soul.md.plan: define phases and current state using templates/project.md.spec: resolve the decision surface, then write templates/spec.md.decide: append one evidence-backed entry using templates/decision.md.design: requires an existing/forge plansurface inventory (## Surfaces); if absent, refuse and recommendplan. Request optional user examples, run or record the configured research sprint, synthesize 2-3 expert directions with tradeoffs and a recommendation, resolve brand and creative gates, then write templates/designer-brief.md and render it through the adapter named byforge.designer_helper.toolunder templates/adapters/.
Use templates/questions.md for every decision gate.
Hard Stops
- Never write directions before the decision gate resolves.
- Never choose a product, scope, brand, privacy, or emotional-framing call for the inventor.
- Never overwrite decision history.
- Never treat a stale or superseded state file as current.
- Never declare a specification ready for Arc before creative-gate and inventor redline approval.
- Never import facts or wording from another project.
What ships with it
10 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.
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.
- 4d ago First seen · 50 lines · 55 tokens per session scan A 08f68d548bbf
forge is a skill published in the GitHub repository emilvaintrub/ShowRunner (2 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 460 once invoked, about $0.0003 per session on Opus 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-31.
Other skills, from other repositories
testing-strategy
Selects the narrowest sufficient test boundary from requirements, repository evidence, and maintenance cost. Use when deciding integration or E2E coverage.
documentation-criteria
Determines which PRD, ADR, Design Doc, and Work Plan a change requires. Use when deciding documentation scope or creating technical documents.
ai-development-guide
Applies root-cause analysis, impact inspection, and completeness checks without expanding approved scope. Use when fixing bugs, refactoring, reviewing quality, or resolving unexpected implementation evidence.
testing
Applies repository-aware TDD, observable test design, and applicable quality checks. Use when changing behavior, writing tests, or reviewing test quality.
coding-rules
Applies repository-aware rules for maintainable implementation, contracts, errors, and refactoring. Use when writing or modifying code.
implementation-approach
Selects the smallest sufficient implementation strategy and verification boundary from current requirements and repository evidence.