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 instructions/khou/showrunner/agents-mdgit clone --depth 1 https://github.com/khou/showrunnerWhat 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.00305 | $0.00305 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
showrunner AGENTS.md 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 yesterday.
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
Learned User Preferences
- Prefer dual-token auth: a shareable/commitable worker token so remote agents can join without cloud secrets; keep the director token secret and alone able to claim direction or mutate admin APIs.
showrunner initshould write the director token to.env, document worker registration from committed showrunner/MCP files, and keep README/SETUP examples aligned.- Onboard may guide optional role specialization via show rules (dedicated workers for art, local tools, etc.) when the user wants that pattern.
- Leave subagent fan-out to workers; directors may nudge workers to use their own subagents without over-documenting ownership mechanics.
- For cross-user worker shows, prefer hard security boundaries beyond protocol rules (identity, admission gates, runtime posture); server-held rules should be mutable only with the director token.
- Keep README, SETUP, and agent-facing instructions in sync whenever the auth or security model changes.
- Product changes belong in the showrunner repo; consumer projects should re-init rather than hand-patching old scaffolding.
Learned Workspace Facts
- Auth uses
SHOWRUNNER_TOKEN(director) andSHOWRUNNER_WORKER_TOKEN(worker); the worker token is intended to be shareable/committable for remote agents. - The maintainer's production Fly app is separate from consumer project Fly apps; names and secrets do not collide.
- Worker role specialization is expressed through show rules, not by showrunner owning or routing subagents.
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.
- yesterday First seen · 16 lines · 305 tokens per session scan A d5242d09301f
showrunner AGENTS.md is an instructions file published in the GitHub repository khou/showrunner (1 stars, last pushed 1mo ago), licensed MIT. It adds 305 tokens to every session, about $0.0015 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.