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/arcnpx skills add emilvaintrub/ShowRunner --skill arcgit 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/arc)<a href="https://agentmods.dev/skills/emilvaintrub/showrunner/arc"><img src="https://agentmods.dev/badge/skills/emilvaintrub/showrunner/arc.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.00073 | $0.00489 |
| Opus 5 | $0.00036 | $0.00244 |
| Sonnet 5 | $0.00015 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
arc 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
Arc
Turn approved direction into verified branch work. Resolve conventions from evidence, escalate product or scope calls, and never merge automatically.
Load
- Read
../core/method.md. - Read the active project's
.claude/showrunner/config.md. - Read method.md.
- For
run, load../core/dispatch.md. - For
verifyormerge, load../core/merge.md. - Load only the templates required by the requested command.
Route
init: inspect repository mechanics and fill the Arc config section.plan: consume approved direction, resolve conventions, and render an implementation prompt.run: executeplan, dispatch a cold implementer, review Step 0, collect evidence, and stop before merge.verify: independently review the exact feature tip and issueSHIP,FIX, orREDESIGN.merge: afterSHIP, required smoke, and explicit approval, execute the shared two-commit ceremony.
Use templates/questions.md for human decisions, templates/spec.md for Arc-owned planning, templates/impl-prompt.md for dispatch, templates/ship-report.md for completion, and templates/merge.md for merge readiness.
Hard Stops
- Never rewrite approved Forge sections 1-8 while consuming sections 9-11.
- Never dispatch before the front-loaded decision gate resolves.
- Never authorize edits before Step 0 approval.
- Never widen scope silently.
- Never accept static inspection as required physical or operational smoke.
- Never issue
SHIPwithout binding the verdict to the exact feature tip. - Never merge without independent
SHIP, required smoke, and explicit human approval. - Never import facts or wording from another project.
What ships with it
7 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 · 49 lines · 73 tokens per session scan A 0bdcdc2a1153
arc is a skill published in the GitHub repository emilvaintrub/ShowRunner (2 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 489 once invoked, about $0.0004 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.
implementation-approach
Selects the smallest sufficient implementation strategy and verification boundary from current requirements and repository 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.