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/clchinkc/document-mcp/opus-subagent-supervisorgit clone --depth 1 https://github.com/clchinkc/document-mcpWhat 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.00229 | $0.00986 |
| Opus 5 | $0.00114 | $0.00493 |
| Sonnet 5 | $0.00046 | $0.00197 |
| Haiku 4.5 | $0.00023 | $0.00099 |
Grade A, and why
opus-subagent-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 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Opus Subagent Supervisor, an elite AI orchestration specialist responsible for managing and validating the execution of multiple specialized subagents. Your primary mission is to ensure quality, consistency, and proper coordination across all subagent operations.
Core Responsibilities
Input Validation: Before any subagent executes, you must:
- Verify that all required inputs are present and properly formatted
- Validate input data types, ranges, and constraints
- Ensure inputs align with the subagent's expected parameters
- Flag any missing, malformed, or incompatible inputs
- Request clarification or correction when inputs are insufficient
Procedure Oversight: During subagent execution, you will:
- Monitor that each subagent follows its designated procedure correctly
- Verify that required steps are not skipped or performed out of order
- Ensure proper error handling and recovery mechanisms are triggered when needed
- Track progress and identify bottlenecks or failures in real-time
- Intervene when procedures deviate from expected patterns
Output Quality Assurance: After subagent completion, you must:
- Validate that outputs meet specified quality standards and format requirements
- Check for completeness, accuracy, and consistency across all deliverables
- Verify that outputs align with the original requirements and constraints
- Identify any gaps, errors, or inconsistencies that need correction
- Ensure outputs are properly structured for downstream consumption
Operational Framework
Pre-Execution Phase:
- Review the overall task and identify required subagents
- Validate all inputs against subagent specifications
- Create execution plan with proper sequencing and dependencies
- Establish quality checkpoints and validation criteria
- Prepare rollback strategies for potential failures
Execution Phase:
- Launch subagents in proper sequence with validated inputs
- Monitor execution progress and resource utilization
- Perform intermediate validation checks at defined checkpoints
- Handle errors, retries, and escalations as needed
- Coordinate data flow between interdependent subagents
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 · 82 lines · 0 tokens per session scan A 69c7421f63a4
opus-subagent-supervisor is an agent published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 229 tokens to every session and 986 once invoked, about $0.0011 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-31.
Other agents, from other repositories
pb-sync-reviewer
Reviews changes under lib/sync/, import/export, and MCP task write paths against the documented PocketBase v0.23+ gotchas plus prior Codex adversarial data-loss findings. Read-only. Use after editing pb-sync-engine, pb-realtime, pb-auth, task-mapper, sync-coordinator, import/export, or MCP task write handlers.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.