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 skills add Obedience-Corp/festival --skill fest-methodologygit 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/skills/obedience-corp/festival/fest-methodology)<a href="https://agentmods.dev/skills/obedience-corp/festival/fest-methodology"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/fest-methodology/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/obedience-corp/festival/fest-methodology"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/fest-methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00419 |
| Opus 5 | $0.00023 | $0.00210 |
| Sonnet 5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
fest-methodology 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 9d 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 Methodology
Festival Methodology is a goal-oriented project management system for human-AI development workflows. It replaces sprints, story points, and time estimates with steps to goals.
Core Concepts
- Festivals: Top-level project containers with a specific goal
- Phases: Major stages (planning, implementation, review), prefixed
NNN_(e.g.,001_PLAN/) - Sequences: Ordered groups of related tasks within a phase, prefixed
NN_(e.g.,01_setup/) - Tasks: Atomic work units as markdown files, prefixed
NN_(e.g.,01_create_schema.md)
Hierarchy
Festival
└── Phase (NNN_UPPER_CASE/)
└── Sequence (NN_lower_snake_case/)
└── Task (NN_lower_snake_case.md)
Lifecycle
planning/ → ready/ → active/ → dungeon/completed/
Key CLI Commands
fest understand methodology # Learn the methodology
fest create festival # Create a new festival
fest next # Get next actionable task
fest task completed # Mark task done
fest commit -m "msg" # Commit with festival traceability
fest validate # Check structure
fest status # View progress
When You Detect Festival Context
If you're working in a directory containing festivals/, or the user references festival methodology concepts, use fest commands rather than manual file manipulation. The CLI handles naming, validation, and traceability automatically.
Always run fest next to determine what to work on rather than manually picking tasks (it respects dependency order).
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.
- 9d ago First seen · 49 lines · 47 tokens per session scan A 64d8052fd3c5
fest-methodology is a skill published in the GitHub repository Obedience-Corp/festival (50 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 419 once invoked, about $0.0002 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 skills, from other repositories
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
workspace-prune-working
Clean up .aiwg/working/ by promoting, archiving, or deleting temporary files.
workspace-realign
Reorganize and update .aiwg/ documentation to reflect current project reality.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
index
Build, query, inspect dependencies, sync Fortemi Core cache, and report status for the searchable index of SDLC artifacts in .aiwg/.