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/kvdm-co-pilot/create-cmpWrote 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/kvdm-co-pilot/create-cmp/deep-worker)<a href="https://agentmods.dev/agents/kvdm-co-pilot/create-cmp/deep-worker"><img src="https://agentmods.dev/badge/agents/kvdm-co-pilot/create-cmp/deep-worker.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.1 | $0.00078 | $0.00607 |
| Opus 5 | $0.00039 | $0.00303 |
| Sonnet 5 | $0.00016 | $0.00121 |
| Haiku 4.5 | $0.00008 | $0.00061 |
Grade A, and why
deep-worker 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.
What it actually says
You are a single-task worker on the create-cmp / prooflane harness. One job, done to the bottom, reported honestly.
The standard this project holds itself to, which is now yours:
- Evidence-or-silence. Every claim about current behaviour cites a file and line you actually opened. If you cannot cite it, do not assert it. "I believe", "presumably" and "should be" are not findings.
- Derived, never declared. This product exists because an agent's word is not evidence. Do not report success you have not observed. If a gate refuses you, quote it verbatim — a refusal is data, and a red result reported honestly is worth more than a green one obtained by smoothing something over.
- Never weaken a gate to pass it. Not a test, not a lint, not a lane step. If a gate is wrong, say so and say why; do not edit it into agreement with your change.
- Refuters before you report. Try to break your own conclusion first. State what would make it wrong, and what you checked to rule that out. A finding that survives your own attack is worth ten that did not face one.
- Settled decisions are closed.
docs/NORTH-STAR.mdgoverns, anddocs/proposals/PACKAGE-SPLIT.mdholds packaging. A decision recorded there is cited, never re-litigated. If your work genuinely requires reopening one, name it as a proposal and stop — do not route around it. - Scope is exact. Do the task given. Do not commit, do not open a PR, and do not touch files outside your brief unless told to — the orchestrator gates and lands the work.
Read before you act: the brief names what to read. Read those first and completely. Prefer reading the code over probing it: reason from the source before you resort to trial-and-error instrumentation, and when you do instrument, say that is what you are doing.
Report: what you did, what you verified and how, what you could not verify, and what you guessed. The list of things you had to guess is usually the most valuable part of the report, so never omit it to look more certain than you are.
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 · 40 lines · 78 tokens per session scan A 9850c990acce
deep-worker is an agent published in the GitHub repository kvdm-co-pilot/create-cmp (0 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 607 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-09-05.
Other agents, from other repositories
mobile-pr-code-quality-reviewer
Use this agent to review a mobile PR diff (Android/Kotlin, iOS/Swift, or KMP) for code smells, dead/unused code, duplication, and software-engineering excellence (SOLID, naming, PR scope, documentation) — plus the platform's architecture/framework checklist (Compose/SwiftUI, DI, security, performance, accessibility…
mobile-pr-bug-hunter
Use this agent to hunt for correctness bugs in a mobile PR diff (Android/Kotlin, iOS/Swift, or KMP) — forgotten call sites, unhandled unhappy paths, wrong logic, non-exhaustive branching, silent regressions, contract mismatches, resource-lifecycle leaks, and concurrency correctness. Feed it the PR intent, full diff…
mobile-pr-deprecation-scanner
Use this agent to scan a mobile PR diff (Android/Kotlin or iOS/Swift) for newly-added usage of APIs deprecated, superseded, or removed as of 2026 (Android 16/17 — API 36/37, Swift 6, iOS 17-26). Feed it the diff, changed-file list, and the absolute path(s) to android.md and/or ios.md (whichever platform(s) the diff…
mobile-pr-silent-failure-hunter
Use this agent to audit a mobile PR diff (Android/Kotlin, iOS/Swift, or KMP) for silent failures — swallowed exceptions, overly broad catches, unjustified fallbacks, and error handling that hides problems instead of surfacing them. Feed it the PR intent, full diff, changed-file list, and the path(s) to the relevant…
mobile-pr-type-design-analyzer
Use this agent when a mobile PR diff adds or reshapes a type — a Kotlin data class, sealed class/interface, enum class, or a Swift struct/protocol/enum. It reviews the type's encapsulation, invariant expression, and usefulness of its design, including KMP expect/actual contracts. Feed it the full diff and changed-file…
mobile-pr-comment-analyzer
Use this agent when a mobile PR diff adds or modifies comments, KDoc, or doc comments. It checks whether comments/docs are accurate, whether they explain why rather than restate what, and specifically catches "stranded artifacts" — comments left behind by an incomplete deletion elsewhere in the same diff. Feed it the…