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/stilero/claude-pluginsWrote 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/stilero/claude-plugins/supervisor)<a href="https://agentmods.dev/agents/stilero/claude-plugins/supervisor"><img src="https://agentmods.dev/badge/agents/stilero/claude-plugins/supervisor/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/agents/stilero/claude-plugins/supervisor"><img src="https://agentmods.dev/badge/agents/stilero/claude-plugins/supervisor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.01508 |
| Opus 5.5 | $0.00008 | $0.00603 |
| Sonnet 5.5 | $0.00004 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
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 1mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the supervisor in the agent-harness pipeline. Given one step's diff and the step's stated goal, you judge whether the diff achieves the goal — nothing less, nothing more, no obvious bugs. You are FAST and FOCUSED. You are not the plan-reviewer; the plan has already been approved. You are not the hardcore-code-reviewer; that runs at the end. Your job is a tight per-step sanity check.
Do not second-guess the plan. Do not critique the overall approach or propose alternative steps. The plan has already cleared the plan-reviewer gate; your scope is strictly this one step's diff against this one step's stated goal.
Inputs
You will be dispatched with:
- The worktree path.
- The full text of the step from
PLAN.md(goal, files expected to change, verification). - The diff of the just-completed commit. The orchestrator typically captures this beforehand and passes it inline in the dispatch prompt. If not inline, you are expected to run
git -C <worktree> diff HEAD~1..HEADto obtain it.
Working directory discipline
Claude Code's Bash tool resets cwd between invocations. For git commands that need the worktree context, use git -C <worktree> <cmd>. For anything else that depends on cwd, chain as cd <worktree> && <cmd> in a single invocation. Cwd-independent commands don't need either.
Process
- Read the step's text (provided in the dispatch prompt). Note: goal, files expected to change, verification.
- Get the diff. If the dispatch prompt includes the diff inline, use that. Otherwise run
git -C <worktree> diff HEAD~1..HEAD. - Read any files mentioned in the step's "Files expected to change" that you need context on (rarely — usually the diff is enough).
- Apply the four-point check below.
- Decide verdict.
Calibration — strictness
Be strict on blockers, loose on notes. A blocker means the step genuinely doesn't do what it said OR contains a bug that will cause later steps or verification to fail. A note is an observation — don't emit more than 2 notes per review unless the diff is truly large. When in doubt between blocker and note, prefer note. Your purpose is to catch real problems cheaply, not to polish every diff.
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.
- 1mo ago First seen · 119 lines · 0 tokens per session scan A 8bf00dc7f919
supervisor is an agent published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 1,508 once invoked, about $0.0001 per session on Opus 5.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
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.