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.
git clone --depth 1 https://github.com/Obedience-Corp/festivalWrote 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/commands/obedience-corp/festival/fest-status)<a href="https://agentmods.dev/commands/obedience-corp/festival/fest-status"><img src="https://agentmods.dev/badge/commands/obedience-corp/festival/fest-status.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.1 | $0.00009 | $0.00068 |
| Opus 5 | $0.00005 | $0.00034 |
| Sonnet 5 | $0.00002 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
fest-status 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 8d 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
Festival Status
Run fest status to show overall festival progress, then fest progress for detailed breakdown.
fest status
Present the results clearly. If the user wants more detail:
fest progress
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.
- 8d ago First seen · 19 lines · 9 tokens per session scan A 4b53422d07c9
fest-status is a command published in the GitHub repository Obedience-Corp/festival (50 stars, last pushed 5d ago), licensed Apache-2.0. It adds 9 tokens to every session and 68 once invoked, about $0.0000 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-30.
Other commands, from other repositories
speckit.companion.specify
Companion specify — spec.md with prioritized user stories.
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
speckit.companion.tasks
Companion tasks — user-story phased task list.
speckit.companion.auto
Companion auto — run the whole pipeline hands-off (specify → plan → tasks → implement → mark-complete), no pauses.
speckit.companion.doctor
Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).