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/sentrynpx skills add emilvaintrub/ShowRunner --skill sentrygit 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/sentry)<a href="https://agentmods.dev/skills/emilvaintrub/showrunner/sentry"><img src="https://agentmods.dev/badge/skills/emilvaintrub/showrunner/sentry.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.00109 | $0.00834 |
| Opus 5 | $0.00055 | $0.00417 |
| Sonnet 5 | $0.00022 | $0.00167 |
| Haiku 4.5 | $0.00011 | $0.00083 |
Grade A, and why
sentry 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry
Find security weaknesses systematically, preserve human risk decisions, and
stop every code fix before main.
Load
- Read
../core/method.md. - Read the active project's
.claude/showrunner/config.md. - Read method.md.
- Load knowledge/catalog.md for sweeps.
- Load knowledge/standards.md only for mapping or refresh.
- Load
../core/dispatch.mdforfix. - Load
../core/merge.mdforverifyormerge. - Load pen-test/SKILL.md for
pen-test. - Load only the template required by the requested command.
Route
init: infer security bindings, preserve shared and sibling config, and optionally create a project security document.sweep <category|all>: perform a read-only categorical review, ingest any configured external live-site scanner evidence such as Code Quality Check, collect configured browser evidence such as Playwright traces and console or network observations, and reconcile findings with accepted-risk and regression memory.fix <finding-id>: resolve human-owned decisions, dispatch one isolated fix, verify evidence, and stop before merge.verify <finding-id>: independently review the exact feature tip against the original finding and regression catalog.accept <finding-id>: append an evidence-backed risk decision with owner, expiry, and revisit trigger.deps: run configured dependency tools and classify direct, transitive, override, and accepted cases.pen-test init|plan|run|validate|retest|report|abort|ingest: route a governed assessment through the nested Pen Test skill.pen-test <report-path>: compatibility alias forpen-test ingest <report-path>.monthly: refresh knowledge, sweep, audit dependencies, age accepted risks, and write one digest without starting fixes.refresh-knowledge: fetch authoritative pins through the configured adapter, cache evidence, and flag drift.merge: after exact-tipSHIP, required smoke, and explicit approval, reuse the shared two-commit ceremony.
What ships with it
35 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.
- agents/openai.yaml 238 B
- knowledge/accepted-risks.md 745 B
- knowledge/catalog.md 6.4 KB
- knowledge/severity-rubric.md 850 B
- knowledge/standards.md 3.2 KB
- method.md 14 KB
- pen-test/agents/openai.yaml 204 B
- pen-test/assets/cleanup.md 597 B
- pen-test/assets/coverage-ledger.md 959 B
- pen-test/assets/finding.md 806 B
- pen-test/assets/report.md 1013 B
- pen-test/assets/retest.md 412 B
- pen-test/assets/rules-of-engagement.md 1.1 KB
- pen-test/assets/scope-manifest.md 1.1 KB
- pen-test/assets/test-plan.md 629 B
- pen-test/method.md 5.5 KB
- pen-test/references/authorization.md 2.3 KB
- pen-test/references/coverage.md 2.2 KB
- pen-test/references/profiles.md 2.8 KB
- pen-test/references/validation.md 1.6 KB
- pen-test/schemas/catalog.schema.json 996 B
- pen-test/schemas/coverage.schema.json 2.0 KB
- pen-test/schemas/engagement.schema.json 5.9 KB
- pen-test/schemas/finding.schema.json 1.6 KB
- pen-test/schemas/retest.schema.json 629 B
- pen-test/SKILL.md 4.2 KB
- templates/accepted-risk.md 640 B
- templates/finding.md 693 B
- templates/fix-prompt.md 827 B
- templates/merge.md 865 B
- templates/monthly-digest.md 576 B
- templates/pen-test-triage.md 582 B
- templates/security.md 1010 B
- templates/ship-report.md 1.8 KB
- templates/sweep-report.md 2.0 KB
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 · 73 lines · 109 tokens per session scan A 9b78966d685f
sentry is a skill published in the GitHub repository emilvaintrub/ShowRunner (2 stars, last pushed 2mo ago), licensed MIT. It adds 109 tokens to every session and 834 once invoked, about $0.0005 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.