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.
git 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/camp-init)<a href="https://agentmods.dev/commands/obedience-corp/festival/camp-init"><img src="https://agentmods.dev/badge/commands/obedience-corp/festival/camp-init/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/commands/obedience-corp/festival/camp-init"><img src="https://agentmods.dev/badge/commands/obedience-corp/festival/camp-init.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00007 | $0.00180 |
| Opus 5.5 | $0.00003 | $0.00072 |
| Sonnet 5.5 | $0.00001 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
camp-init 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 1mo 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
Initialize a Camp
Create a new camp with the standard directory structure. A camp was previously called a campaign; camp init is the same command either way.
camp init {{name}}
This creates:
projects/: git submodule project directoryfestivals/: festival methodology workspaceworkflow/: intents, design docs, code reviewsdocs/: human-authored documentation.campaign/: camp metadata directory (that path is stable; do not rename it)
After init, remind the user to set up shell integration:
eval "$(camp shell-init zsh)"
eval "$(fest shell-init zsh)"
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.
- 1mo ago Changed · -1 tokens per session b104a6c38772
- 1mo ago First seen · 31 lines · 8 tokens per session scan A 0394b0b50c5d
camp-init is a command published in the GitHub repository Obedience-Corp/festival (78 stars, last pushed yesterday), licensed Apache-2.0. It adds 7 tokens to every session and 180 once invoked, about $0.0000 per session on Opus 5.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
interactive-planning
File-based planning with interactive gates + native task tracking. Supports task-based (single plan file) and spec-driven (multi-file specs with manifest) modes. Phase/Sprint/Spec hierarchy with dependency DAG.
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).
daily-standup
Génération Résumé Daily Stand-up.