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-understand)<a href="https://agentmods.dev/commands/obedience-corp/festival/fest-understand"><img src="https://agentmods.dev/badge/commands/obedience-corp/festival/fest-understand.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.00021 | $0.00216 |
| Opus 5 | $0.00010 | $0.00108 |
| Sonnet 5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
fest-understand 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
Learn Festival Methodology
Run fest understand commands to teach the user (or yourself) about the methodology.
If no topic specified, start with the overview:
fest understand methodology
For a specific topic:
fest understand {{topic}}
Available topics:
methodology: Core principles and philosophystructure: Three-level hierarchy (phases, sequences, tasks)tasks: How to write and execute tasksrules: Naming conventions and structural rulestypes: Festival and phase typesgates: Quality gates at sequence boundaries
Present the output clearly. If the user has follow-up questions, use additional fest understand commands or read the methodology docs directly.
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 · 35 lines · 21 tokens per session scan A 6efdb2f59968
fest-understand is a command published in the GitHub repository Obedience-Corp/festival (50 stars, last pushed 5d ago), licensed Apache-2.0. It adds 21 tokens to every session and 216 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
explain
Explain code, concepts, or system behavior with adjustable depth levels.
create-onboarding-guide
Command "create-onboarding-guide" from qdhenry/Claude-Command-Suite, covering create onboarding guide and instructions.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
refactor
Analyze code for SOLID violations and suggest targeted improvements.
generate-tests
Generate comprehensive tests for specified code.