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/plugins/obedience-corp/festival/claude-plugin)<a href="https://agentmods.dev/plugins/obedience-corp/festival/claude-plugin"><img src="https://agentmods.dev/badge/plugins/obedience-corp/festival/claude-plugin/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/plugins/obedience-corp/festival/claude-plugin"><img src="https://agentmods.dev/badge/plugins/obedience-corp/festival/claude-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
festival 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 8d 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
{
"name": "festival",
"version": "1.4.1",
"description": "Festival Methodology: goal-oriented project management for human-AI development workflows. Provides fest and camp CLI integration, automatic installation, and methodology guidance.",
"author": {
"name": "Obedience Corp",
"url": "https://obediencecorp.com"
},
"homepage": "https://github.com/Obedience-Corp/festival",
"repository": "https://github.com/Obedience-Corp/festival",
"license": "Apache-2.0",
"keywords": [
"festival",
"project-management",
"ai-workflows",
"fest",
"camp",
"methodology"
],
"types": "./types/index.d.ts",
"userConfig": {
"planningTakeover": {
"type": "boolean",
"title": "Festival planning takeover",
"description": "Inside a camp, hide the Plan agent and deny plan mode and the session todo list so planning goes through Festival.",
"default": false
}
}
}
What it installs
The manifest is a name and a version. 11 commands, 2 hooks travel with it, and installing the plugin installs all of them — 151 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command festival-plan A 20 tokens
- Command fest-create A 14 tokens
- Command camp-init A 7 tokens
- Command camp-intent A 18 tokens
- Command fest-commit A 11 tokens
- Command fest-understand A 21 tokens
- Command fest-show A 17 tokens
- Command fest-validate A 10 tokens
- Command fest-list A 12 tokens
- Command fest-next A 12 tokens
- Command fest-status A 9 tokens
- Hook PreToolUse A not measured
- Hook SessionStart A not measured
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.
- 8d ago Changed · +9 lines 4e40c314fd3c
- 1mo ago First seen · 21 lines scan A b5079a3ab2ba
festival is a plugin published in the GitHub repository Obedience-Corp/festival (69 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
prd-workflow
RFC-driven development workflow: vague idea → verified PRD → features → rules → sequenced RFCs → reviewed, tested code.
bounty-board
Turns your repo's tech debt into an aging bounty economy. A SessionStart hook scans tracked files and prices each TODO/FIXME/HACK/skip as a wanted-poster bounty whose XP grows with its git-blame age, injects the top 3 as opportunistic side quests, and, via a PostToolUse hook, verifies and pays out bounties that…
standup-autopilot
Turns what your agents ACTUALLY did into a standup: captured from session transcripts (not commits/tickets, which miss uncommitted work, real test exit codes, and unresolved errors) and rolled up cross-repo. Stop/SessionEnd snapshot each session's outcome (task, branch + diffstat, tests + exit codes, PRs, blockers) to.
people-management
AI-augmented management tooling for people managers. Surfaces the right context at the right time: before meetings, during 1:1 prep, when triaging messages, or reviewing customer status. Adapts to your org's performance and management frameworks. Augments managers, never automates.
instruction-placement
Routes agent instructions to the surface that loads them at the right time. audit finds conventions narrower than the always-loaded CLAUDE.md or AGENTS.md, or stranded in docs Claude never loads, and proposes a destination with a validated paths glob; safety content is never demoted. realign applies each move and…
ops
Structured non-code project management for Claude Code: planning, execution, knowledge persistence, and autonomous work loops for research, strategy, and content projects. 9 skills, 5 agents, 7 commands.