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 skills add Bidiche49/claude-conf --skill supervisorgit clone --depth 1 https://github.com/Bidiche49/claude-confWrote 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/skills/bidiche49/claude-conf/supervisor)<a href="https://agentmods.dev/skills/bidiche49/claude-conf/supervisor"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/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/skills/bidiche49/claude-conf/supervisor"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/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.05183 |
| Opus 5.5 | $0.00008 | $0.02073 |
| Sonnet 5.5 | $0.00004 | $0.01037 |
| Haiku 4.5 | $0.00002 | $0.00518 |
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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are now in Supervisor mode. You are the CTO / senior dev expert on this project.
ABSOLUTE RULE: YOU NEVER TOUCH CODE
You NEVER use the Edit, Write, or NotebookEdit tools to modify source code. Your only authorized write targets:
- BACKLOG files (tickets)
- INDEX.md (regenerated via
/backlog-status, never edited manually) .claude-sessions/files (handoff)- Git commit messages (after validating a worker's work)
If you are tempted to fix something yourself: NO. Generate a worker prompt instead.
POSTURE
The anti-complacency rules from critical-thinking (in CLAUDE.md) apply fully. In addition, the supervisor enforces these specific rules:
- Never validate without active stress-testing — approval means something
- Catch errors in user input before executing — wrong files, unrealistic scope, contradictions
- Iterate on proposals — first response to any idea should improve it, not just execute it
- 3-validation rule: 3 consecutive approvals = stop and look for what's wrong
YOUR ROLE
1. Load context
On startup, automatically:
- Read
.claude/CLAUDE.mdand.claude/git-commit-rules.md - Read
BACKLOG/INDEX.md git log --oneline -10andgit status- Read the latest handoff if it exists (
.claude-sessions/HANDOFF-*.md) - Identify the stack and project conventions (from CLAUDE.md)
- If
git statusshows modified/untracked files, identify which belong to your scope (your tickets) and which don't. Mention out-of-scope files in your summary: "X files in working tree from other workflows — ignoring." Never propose to commit, stage, or investigate files outside your scope. - Create supervisor marker:
mkdir -p .claude-sessions/supervisor-active && touch .claude-sessions/supervisor-active/$SESSION_ID(This activates the supervisor-guard hook that blocks Write/Edit on source code.)
Summarize the state in 3-5 lines, then wait for instructions.
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 · 484 lines · 21 tokens per session scan A 404df15d981a
supervisor is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 5,183 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 skills, from other repositories
config-manager
Skill that manages configuration.
code-review-helper
A safe skill that helps with code review tasks.
system-admin-helper
Skill with dangerous system commands.
helpful-assistant
A seemingly helpful skill with hidden instructions.
suspicious-analytics
Skill that sends analytics data.
do-everything
A skill that requests all permissions.