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-planninggit 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-planning)<a href="https://agentmods.dev/skills/obedience-corp/festival/fest-planning"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/fest-planning/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-planning"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/fest-planning.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.00034 | $0.00730 |
| Opus 5 | $0.00017 | $0.00365 |
| Sonnet 5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
fest-planning 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Festival Planning
Start Here
fest understand methodology
fest understand structure
fest understand tasks
fest understand rules
fest types festival
Naming Rules (Automation-Critical)
- Phase dir:
NNN_UPPER_CASE/(e.g.,001_IMPLEMENT/) - Sequence dir:
NN_lower_snake_case/(e.g.,01_auth_module/) - Task file:
NN_lower_snake_case.md(e.g.,01_create_handler.md)
Every sequence should include SEQUENCE_GOAL.md.
Festival Types (Choose Before Scaffolding)
Use fest types festival / fest types festival show <type> as source of truth.
standard: Full planning + implementation (recommended for most work)implementation: Execution-only (use when requirements already exist)research: Investigation and explorationritual: Recurring processes
fest create festival --name "<name>" --type standard
fest create festival --name "<name>" --type implementation
fest create festival --name "<name>" --type research
fest create festival --name "<name>" --type ritual --dest ritual
Phase Types
planning: Workflow phase for architecture/decisions (WORKFLOW.md, no numbered sequences)research: Investigation and findingsingest: Normalizing incoming context/specsimplementation: Sequence-driven coding (numbered sequences/tasks, quality gates)review: Freeform acceptance/signoffnon_coding_action: Operational actions
fest create phase --name "001_IMPLEMENT" --type implementation
Create / Promote
fest create festival
fest create phase
fest create sequence
fest create task
fest promote
fest validate
Link + Navigation
fest link [path]
fest link --show
fest links
fest unlink
# Shell helper after eval "$(fest shell-init zsh)"
fgo
fgo project
fgo fest
Scaffolding from Plan
fest scaffold from-plan --plan STRUCTURE.md --name my-festival
Standalone WORKFLOW.md (Outside a Festival)
For a short, repeatable step checklist that does not need a full festival
(phases/sequences/tasks), scaffold a standalone WORKFLOW.md instead:
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.
- 10d ago First seen · 111 lines · 34 tokens per session scan A 298385ad2aba
fest-planning is a skill published in the GitHub repository Obedience-Corp/festival (49 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 730 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/.