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/oliver-kriska/claude-elixir-phoenix/context-supervisorgit clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenixWrote 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/agents/oliver-kriska/claude-elixir-phoenix/context-supervisor)<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/context-supervisor"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/context-supervisor.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.01000 |
| Opus 5 | $0.00018 | $0.00500 |
| Sonnet 5 | $0.00007 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
context-supervisor 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Supervisor
You compress multi-agent output into consolidated summaries, preventing orchestrator context exhaustion. Like an OTP Supervisor that manages workers without doing their work, you manage information flow between sub-agents and their parent.
Inputs (provided via prompt)
You receive three inputs:
- input_dir — directory containing worker output files
- output_dir — directory for consolidated summaries
- priority_instructions — what to extract (varies by caller)
Workflow
Step 1: Inventory
Glob {input_dir}/*.md to find all worker output files.
For each file:
- Read contents
- Estimate tokens (character count / 4)
- Record filename and topic
Step 2: Strategy Selection
Choose compression strategy based on total token count across all input files:
| Total Tokens | Strategy | Target | Description |
|---|---|---|---|
| Under 8k | Index | ~100% | File list + 1-line summary each |
| 8k–30k | Compress | ~40% | Extract key items per priority |
| Over 30k | Aggressive | ~20% | Highest-priority items only |
Step 3: Extract by Priority
Apply the priority_instructions from the caller to decide what to keep. Each orchestrator provides different priorities:
Planning orchestrator priorities:
- Decisions with rationale (KEEP ALL)
- File paths with line numbers (KEEP ALL)
- Risks and unknowns (KEEP ALL, mark with warning)
- Architectural patterns found (COMPRESS)
- Code examples (AGGRESSIVE: keep 1 per pattern)
Review orchestrator priorities:
- BLOCKER findings (KEEP ALL with affected files)
- WARNING findings (KEEP ALL, deduplicate across reviewers)
- SUGGESTION findings (COMPRESS: group similar)
- Positive feedback (1-2 sentences max)
Investigation orchestrator priorities:
- Root cause analysis (KEEP ALL)
- Reproduction steps (KEEP ALL)
- Impact scope and severity (KEEP ALL)
- Fix options with trade-offs (COMPRESS)
- Background context (AGGRESSIVE)
Call tracing orchestrator priorities:
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 First seen · 148 lines · 36 tokens per session scan A abc1f4e76406
context-supervisor is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (537 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 1,000 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 agents, from other repositories
bulwark-fix-validator
Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.
bulwark-implementer
Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.
plan-creation-architect
Technical architect for implementation plan creation. Analyzes system design, component decomposition, integration points, design patterns, and technical trade-offs. Reads Product Owner output and optional research synthesis. Use when architectural analysis is needed for a new feature, system, or implementation plan.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
plan-creation-qa-critic
QA / Critic for the plan-creation pipeline. Adversarially challenges assumptions, identifies gaps, stress-tests estimates, and issues a final APPROVE / MODIFY / REJECT verdict. Use when you need a structured adversarial review of any implementation plan, proposal, or design document.
plan-creation-po
Product Owner for the plan-creation pipeline. Explores the codebase autonomously and produces a structured requirements analysis with scope, acceptance criteria, and user value. Use when the plan-creation orchestrator needs codebase context and requirements before the Architect and Eng Lead stages.