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 campaign-workflowsgit 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/campaign-workflows)<a href="https://agentmods.dev/skills/obedience-corp/festival/campaign-workflows"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/campaign-workflows.svg" alt="Measured on agentmods" 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.00041 | $0.00339 |
| Opus 5 | $0.00020 | $0.00169 |
| Sonnet 5 | $0.00008 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
campaign-workflows 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 4d 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
Camp Workflows
A camp was previously called a campaign; these commands work the same either way.
All workflow commands here are camp, not fest.
Use camp for intents, dungeons, and workflow collections. fest is for
festival planning and execution.
Intents
camp intent add "idea"
camp intent list
camp intent move <id> active
camp intent promote <id>
camp intent archive <id>
Dungeon
camp dungeon crawl
crawl is interactive/TTY-oriented.
Workflow Collections
A workflow collection is a camp directory under workflow/<type>/ with its
own navigation config and workitem types.
camp workflow list # user-created collections
camp workflow show <name> # config and recent workitems
camp workflow create <name> # create a custom collection
camp workflow doctor # report workflow surface inconsistencies
camp workflow sync # repair auto-fixable doctor findings
Item status moves are camp intent move <id> <status>, not a workflow command.
Common Mistakes
- Running
festcommands for intent or workflow-collection operations. - Deleting old work instead of moving it to dungeon statuses.
- Promoting intents before they are sufficiently shaped.
- Reaching for a
camp flowcommand: the surface iscamp workflow.
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.
- 4d ago Changed · +2 lines · +2 tokens per session 60d4b78431da
- 8d ago First seen · 52 lines · 39 tokens per session scan A 84f1ff69ba3f
campaign-workflows is a skill published in the GitHub repository Obedience-Corp/festival (50 stars, last pushed 5d ago), licensed Apache-2.0. It adds 41 tokens to every session and 339 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/.