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 agentmods add agents/obedience-corp/festival/codexgit clone --depth 1 https://github.com/Obedience-Corp/festivalWhat 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 | $0.00000 | $0.01643 |
| Opus 5 | $0.00000 | $0.00822 |
| Sonnet 5 | $0.00000 | $0.00329 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade C, and why
codex scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/Obedience-Corp/festival/main/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/Obedience-Corp/festival/main/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex
Codex runs Festival through a plugin that carries the skills and a session-start hook. The loop is the same fest next loop it is everywhere else. The plugin's job is narrow: make sure the fest and camp CLIs exist, and make sure the agent knows the vocabulary.
Order matters. Install the binaries first, then open a campaign, then install the plugin.
1. Install Festival
Pick one:
# Homebrew
brew install --cask Obedience-Corp/tap/festival
# npm, pnpm, or bun
npm install -g @obedience-corp/festival
# Shell script
curl -fsSL https://raw.githubusercontent.com/Obedience-Corp/festival/main/install.sh | bash
Then check all three binaries answer:
fest --version
camp --version
festival --version
If either one is missing or resolves somewhere you did not expect, festival doctor reports the installer's view of your PATH, sources, and receipts. Full install options are on the installation page.
The plugin's session-start hook installs these too, so this step is belt and braces. Doing it by hand means your first session works before the hook has run once.
2. Open a campaign
A campaign is the directory Festival works in. Create one and stay at its root:
mkdir my-campaign && cd my-campaign
camp init
camp init writes the campaign layout, initializes git, creates the festivals tree, and writes an AGENTS.md at the root. That last file is the one Codex reads as persistent instructions, which is why section 6 is worth reading before you start editing it.
3. Install the Festival plugin
From a shell, which is the form verified for this page:
codex plugin marketplace add Obedience-Corp/festival
codex plugin add festival@festival
codex plugin list
From inside a Codex session, which is the form the plugin bundle documents:
/plugin marketplace add Obedience-Corp/festival
/plugin install festival
Note the verb. Non-interactively it is codex plugin add; there is no codex plugin install. The in-session slash command is spelled /plugin install. Both are correct in their own context.
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 · 136 lines · 0 tokens per session scan C 3e1a4703e146
codex is an agent published in the GitHub repository Obedience-Corp/festival (48 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,643 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
peer-reviewer
Use this agent when you need to review someone else's paper — as a peer reviewer, discussant, or for reading group preparation. This agent reads the PDF carefully using split-pdf methodology, spawns parallel sub-agents for citation validation, novelty assessment, and methodology review, scans for hidden prompt…
tools
Tools give agents the ability to interact with the outside world — reading files, making HTTP requests, connecting to MCP servers, calling APIs, or running custom Python functions. They are configured in the tools list of a role definition. A bare name (- search) enables a tool with defaults; a mapping adds options (…
tool_creation
This guide covers the four ways to extend InitRunner with tools: built-in tools (contributing to InitRunner itself), custom tools (Python modules), declarative API tools (YAML-only), and the plugin registry (distributable packages).
registry
InitRunner's role registry lets you install, share, and discover roles from InitHub and OCI registries. Roles are downloaded, validated, and saved to /.initrunner/roles/ where they integrate automatically with the CLI.
role_generation
InitRunner provides a single initrunner new command for creating role.yaml files. It supports multiple seed modes (templates, AI generation, examples, hub bundles, or local files) and an interactive refinement loop for iterating on the YAML before saving. Run with no arguments in a terminal and it shows a guided start…
code-explainer
Explains complex code in clear, understandable terms. Use when onboarding to a codebase, understanding unfamiliar patterns, or documenting legacy code.