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-structuregit 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-structure)<a href="https://agentmods.dev/skills/obedience-corp/festival/campaign-structure"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/campaign-structure/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/campaign-structure"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/campaign-structure.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.00044 | $0.00547 |
| Opus 5 | $0.00022 | $0.00273 |
| Sonnet 5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
campaign-structure 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Camp Structure
A camp was previously called a campaign; the layout below is the same either way.
Placement Rules
- Raw idea / bug / future work / quick capture:
.campaign/intents/inbox/(usecamp intent add) - Enriching or preparing for execution:
.campaign/intents/active/ - Ready for structured work:
.campaign/intents/ready/→ promote to festival - Structured multi-phase execution:
festivals/ - Internal design, architecture, or deep exploration:
workflow/design/ - User-facing documentation:
docs/ - Research, analysis, and exploration notes:
workflow/explore/ - Archive / defer / killed:
.campaign/intents/dungeon/or top-leveldungeon/
Critical Distinctions
.campaign/intents/(especiallyinbox/) is the primary capture surface for new ideas, bugs, and tasks.workflow/design/is for thoughtful internal design documents and specs.festivals/is for planned, phased execution (not raw ideas).docs/is user-facing;workflow/explore/is internal.
Canonical reference: .campaign/intents/OBEY.md
Layout Snapshot (Current)
.campaign/
├── intents/ # Idea capture (inbox / active / ready / dungeon)
│ └── OBEY.md # Authoritative intent guide
├── quests/ # Long-lived working contexts
└── skills/ # Camp-specific agent skills (loaded at runtime)
projects/ # Git submodules (the actual codebases)
workflow/
├── code_reviews/
├── pipelines/
├── design/ # Design documents & specs
└── explore/ # Historical research notes
festivals/ # Festival methodology (planning + active)
docs/ # User-facing documentation
dungeon/ # Top-level archive
Common Mistakes
- Putting raw ideas directly into
festivals/orworkflow/design/without going through intents first. - Treating
docs/as the place for internal specs (useworkflow/design/or.campaign/intents/). - Creating ad-hoc top-level directories instead of using the established taxonomy.
- Forgetting that
cgo inow navigates to.campaign/intents/.
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 Changed · +17 lines · +2 tokens per session d3b3d6edd011
- 9d ago First seen · 40 lines · 42 tokens per session scan A b46290cad5d6
campaign-structure is a skill published in the GitHub repository Obedience-Corp/festival (50 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 547 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
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.
activity-log
Query and manage the unified .aiwg/activity.log chronological record of AIWG-managed workflow operations.
checkpoint
Create, list, or recover mid-workflow checkpoints so interrupted work resumes from a known-good position.
mention-conventions
Display @-mention naming conventions and placement rules.
validate-metadata
Validate AIWG extension definitions against the metadata schema and report errors with field names, line numbers, and remediation hints.