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 skills/joymin5655/agent/supervisenpx skills add joymin5655/Agent --skill supervisegit clone --depth 1 https://github.com/joymin5655/AgentWrote 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/joymin5655/agent/supervise)<a href="https://agentmods.dev/skills/joymin5655/agent/supervise"><img src="https://agentmods.dev/badge/skills/joymin5655/agent/supervise.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.00077 | $0.04260 |
| Opus 5 | $0.00039 | $0.02130 |
| Sonnet 5 | $0.00015 | $0.00852 |
| Haiku 4.5 | $0.00008 | $0.00426 |
Grade A, and why
supervise 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/supervise
Goal
Take a written plan (~/.agent/plans/<slug>.md with Wave 1..N sections)
and run it end-to-end, dispatching the right specialist agent for each
wave, auditing after each wave, and aborting on risk-area violations.
Modes
| Mode | Behavior |
|---|---|
/supervise <slug> |
Default: full-auto. Dispatch, audit, advance. Stops on Wave fail or safeguard. |
/supervise <slug> --goal-mode |
Tracks state in SQLite via core/infra/supervisor-goal.sh. Resumable across sessions. Requires sqlite3 + jq (the script exits 127 without them — see README Prerequisites). |
/supervise <slug> --auto-push |
Each wave commits + pushes + opens PR. User merges. |
/supervise <slug> --auto-merge |
Each wave commits + pushes + admin-merges via auto-ship.sh. |
/supervise <slug> --verify-blocking |
Each wave's 2d audit also runs core/infra/completion-gate.sh with AGENT_VERIFY_BLOCKING=block — a REFUTED completion claim STOPs the wave (default without this flag: dryrun, logs only, never blocks). |
Permission friction (plan-scope-allow prerequisite)
/supervise does not grant itself permissions. Whether wave edits hit the
native permission prompt is decided by the plan-scope-allow gate
(docs/gate-registry.md), which is active only when AGENT_PLAN_ALLOW_MODE=on
is exported, or — with the env unset — when the workspace resolves to the
personal trust tier (docs/customization.md § Trust tiers). In collab
workspaces, expect a prompt per edit; prefer report-first waves there.
Coverage is Write/Edit/MultiEdit only — Bash/MCP wave commands always keep
their own gates and prompts (extension is backlog LE-1). Hard safeguards
(risk-area abort, R4 mutex, gitleaks, test-failure abort) bind in every tier
and every mode, including full-auto.
Dispatch pre-flight (before any edit wave leaves the main loop)
A dispatched subagent cannot answer a native permission prompt, and a background dispatch auto-denies any tool call that would prompt — so an edit wave dispatched without cleared permissions doesn't fail loudly, it silently loses its Edit/Write calls and reports garbage. Before dispatching an execution (file-editing) wave, confirm at least one of:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 317 lines · 77 tokens per session scan A 362ac17f9939
supervise is a skill published in the GitHub repository joymin5655/Agent (2 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 4,260 once invoked, about $0.0004 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 skills, from other repositories
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
background-watch-hook
Use vibe watch to run a managed Harness waiter that returns to the same conversation later. Best for reviews, CI, files, logs, and other wait-now-continue-later workflows.
pr-delivery-loop
The implementation-lane standard for delivering a PR across the Avibe repositories (avibe, avibe-backend, avibe-docs, avault, and vault-sandbox) — branch/scope rules, contracts, Codex-bot review-loop discipline, and close-out criteria. Use this skill for every implementation task in these repos, regardless of agent…
use-avibe-harness
Use Avibe Harness for durable Agent delegation, Sessions, scheduled Tasks, Watches, Runs, queues, and work that must continue beyond the current turn.
use-show-pages
Build, inspect, update, or share an Avibe Show Page when a visual explanation, diagram, dashboard, report, or interactive prototype would materially help.
use-avibe-vault
Use Avibe Vault for API keys, tokens, passwords, protected credentials, authenticated HTTP requests, or digest signing without exposing secret values to the agent.