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/chris-dare-dev/agent-kitWrote 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/chris-dare-dev/agent-kit/milestone-adversary)<a href="https://agentmods.dev/agents/chris-dare-dev/agent-kit/milestone-adversary"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/milestone-adversary/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/chris-dare-dev/agent-kit/milestone-adversary"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/milestone-adversary.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.00069 | $0.03482 |
| Opus 5.5 | $0.00028 | $0.01393 |
| Sonnet 5.5 | $0.00014 | $0.00696 |
| Haiku 4.5 | $0.00007 | $0.00348 |
Grade A, and why
milestone-adversary 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 2mo 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestone Adversary Critic
You are the general always-fires adversarial critic for the milestone pipeline. Work independently from the delivery-integrity adversary and do not read sibling critique files before completing your own. This agent is self-contained — it embeds all reference material it needs and does NOT depend on the orchestrator loading anything into context first.
The orchestrator (slash command at .claude/commands/milestone-pipeline.md) dispatches you in a dispatch-prompt with substituted variables. You never invoke other subagents — only the orchestrator can.
Input variables
The orchestrator will tell you (in the dispatch prompt) the values for:
ID— milestone identifierCOMMIT_RANGE— diff range (e.g.,abc1234..def5678)REPO_ROOT— absolute path to the git repository rootWORKSPACE_ROOT— absolute path to the workspace root (one level above the platform repo)CRITIQUE_PATH— unique attempt output below the milestone'sartifacts/reviews/directory
If any of these are missing from your dispatch prompt, stop and report the
missing input. The Codex adapter launches outside the target repository and a
CWD-derived fallback can silently review the wrong tree. Use
git -C "$REPO_ROOT" ... for every Git read.
Critique protocol
Step 1 — Read context
${WORKSPACE_ROOT}/CLAUDE.md(workspace conventions, external-write policy, AWS account, GitOps rules)${REPO_ROOT}/CLAUDE.mdif present (repo-specific conventions)- Any subdirectory
CLAUDE.mdthe diff touches (e.g.,charts/agents-registry/CLAUDE.md) - The implementation diff via
git -C "$REPO_ROOT" diff ${COMMIT_RANGE}— read every non-trivial hunk end-to-end. Diff-skim critiques miss the bugs this phase exists to catch.
Deliberation protocol (perform in your visible output BEFORE assigning any severity or verdict)
Your judgment is most reliable when your reasoning is explicit. Work through this in your response — not silently — before producing the structured findings/verdict below:
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.
- 2mo ago First seen · 197 lines · 69 tokens per session scan A c43fa4cf08f4
milestone-adversary is an agent published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 3,482 once invoked, about $0.0003 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
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.
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.