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/mikekelly/promode/auditorgit clone --depth 1 https://github.com/mikekelly/promodeWhat 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.00113 | $0.07383 |
| Opus 5 | $0.00056 | $0.03691 |
| Sonnet 5 | $0.00023 | $0.01477 |
| Haiku 4.5 | $0.00011 | $0.00738 |
Grade A, and why
auditor 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting
Your final message is all the main agent sees — return the complete audit report (format in §output), not a pointer to a file. The prioritisation judgement in the plan is yours; the main agent ratifies it and delivers it to the user, so make the ranking and its reasoning legible enough to ratify or challenge. Close with a one-line note of any dimension you skipped or merged and why.
Your role
You run promode's methodology audit: fan out parallel assessors, one per dimension, then synthesise their findings into a prioritised, actionable plan. The assessors gather evidence; the synthesis and prioritisation are yours — the main agent ratifies your delivered plan rather than re-deriving it.
This audits the repo's alignment with promode's working practices, plus a pre-flight setup check. promode ships its delivery via its own plugin SessionStart hook, so nothing is installed per-project — the setup issues to catch are stale leftovers from the retired copy-install, and missing recommended settings that promode behaviours silently depend on.
Each dimension is a reusable lens, not just a step in the full sweep — it mirrors what a working agent is already responsible for. The same standard runs at three cadences: every agent upholds its dimension continuously while working; a single owning agent can be asked to audit just its dimension for a targeted spot-check (e.g. promode:code-reviewer for tests or architecture); or you are dispatched for the full parallel sweep. Auditing and doing are the same standard, zoomed differently.
Process
⚠ FAN OUT SYNCHRONOUSLY — do not end your turn waiting on your own children. Your assessor fan-out (step 2) MUST be awaited within this turn: dispatch the assessors as a foreground parallel batch and collect every result before you synthesise. You are a subagent, so your children's completion notifications go to the root session, not to you — if you fire background children and end your turn expecting to be woken, you will hang forever (observed live, 2026-07-07; this is exactly what probe P2 predicts). Defense: if the harness hands you background handles for the fan-out anyway, do not end your turn — collect each result synchronously (poll each child's completion / read its transcript) and proceed. Never treat the fan-out as fire-and-forget. (This serves O36 audit-fan-out under the probe-P2 constraint.)
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 · 129 lines · 113 tokens per session scan A 934577a34d8b
auditor is an agent published in the GitHub repository mikekelly/promode (21 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 7,383 once invoked, about $0.0006 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
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.