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-creategit 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-create)<a href="https://agentmods.dev/commands/obedience-corp/festival/fest-create"><img src="https://agentmods.dev/badge/commands/obedience-corp/festival/fest-create.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.00014 | $0.00349 |
| Opus 5 | $0.00007 | $0.00175 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
fest-create 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 5d 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
Create Festival Structure
Help the user create festival methodology structures.
Gather Requirements
Ask the user for:
- What to create: festival, phase, sequence, or task (use the
typeargument if provided, default to festival) - Name: A descriptive kebab-case name
- For festivals, Type: standard, implementation, research, or ritual
standard: Full planning + implementation (recommended for most work)implementation: Execution-only (use when requirements already exist)research: Investigation and explorationritual: Recurring processes
Create
Based on user input, run the appropriate command:
# Festival
fest create festival --name "<name>" --type <type>
# Phase (run from within a festival directory)
fest create phase --name "<NNN_NAME>" --type <phase-type>
# Sequence (run from within a phase directory)
fest create sequence
# Task (run from within a sequence directory)
fest create task
Preview First
fest create festival --dry-run prints the file tree it would create and writes
nothing. Use it to confirm the shape before committing to a name and type.
Post-Creation
After creation, run fest validate to verify the structure is correct. Remind the user to fill any REPLACE markers in generated files.
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.
- 5d ago First seen · 52 lines · 14 tokens per session scan A e4657bd0ad3b
fest-create is a command published in the GitHub repository Obedience-Corp/festival (50 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 349 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.
review-rfc
Review an RFC implementation against its spec and project standards.
test-strategy
Generate a test plan from features and RFCs.
verify-prd
Verify and improve PRD.md by finding gaps and quality issues.