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.
/plugin marketplace add Obedience-Corp/festivalnpx agentmods add plugins/obedience-corp/festival/claude-plugingit clone --depth 1 https://github.com/Obedience-Corp/festivalGrade 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 2d 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.3.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"
]
}
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.
- 2d ago First seen · 21 lines scan A b5079a3ab2ba
festival is a plugin published in the GitHub repository Obedience-Corp/festival (48 stars, last pushed 3d ago), 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
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.
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…
genie
Human-AI partnership for Claude Code. Share a terminal, orchestrate workers, evolve together. Brainstorm ideas, turn them into wishes, execute with /work, validate with /review, and ship as one team.
claude-craft
Multi-stack framework for Claude Code teams: 12 stacks, BMAD v6 sprint workflow, browser QA automation, and Kanban — for tech leads adopting Claude Code with their team.
atlas-session-lifecycle
Agent Teams-based session lifecycle with AtlasCoin bounty verification.
servicenow
ServiceNow admin toolkit — incidents, CMDB, update sets, table explorer. 19 MCP tools + 4 guided skills.