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 commands/obedience-corp/festival/fest-commitgit clone --depth 1 https://github.com/Obedience-Corp/festivalWhat 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.00011 | $0.00202 |
| Opus 5 | $0.00005 | $0.00101 |
| Sonnet 5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
fest-commit 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
Festival Commit
Commit with festival task traceability. Always prefer this over raw git commit when working inside a festival.
If no message argument provided, ask the user for one. Then:
fest commit -m "<message>"
When the festival or its sequence has a linked project, this one command covers
both sides: it makes a project commit for the project's changes (skipped when the
project is clean) and a campaign root commit for the festival-scoped files. Do not
run camp p commit first and fest commit after.
If not currently inside a festival context, fall back to suggesting camp p commit
for project submodule work or camp commit for campaign root changes. Raw
git commit is forbidden inside a campaign workspace.
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 · 28 lines · 11 tokens per session scan A 37ad0bd5ba5d
fest-commit is a command published in the GitHub repository Obedience-Corp/festival (48 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 202 once invoked, about $0.0001 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
workflow-status
Report which workflow artifacts exist and recommend the next step.
generate-rfcs
Break the PRD into sequential implementation RFCs.
generate-rules
Generate development rules and standards into RULES.md.
manage-changes
Analyze and integrate PRD changes mid-development.
review-rfc
Review an RFC implementation against its spec and project standards.
test-strategy
Generate a test plan from features and RFCs.