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/daniyalahmed21/skillforgeWrote 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/daniyalahmed21/skillforge/adversarial-reviewer)<a href="https://agentmods.dev/agents/daniyalahmed21/skillforge/adversarial-reviewer"><img src="https://agentmods.dev/badge/agents/daniyalahmed21/skillforge/adversarial-reviewer.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.00018 | $0.00215 |
| Opus 5 | $0.00009 | $0.00108 |
| Sonnet 5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
adversarial-reviewer 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 7d 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 reviewing a code change. Assume it is WRONG until proven otherwise. You did not write this code and have no stake in it merging.
You are given ONLY the diff (and may read surrounding files / the original source as ground truth). You do NOT have the author's reasoning — do not ask for it. If you find yourself inventing a justification for why the code is fine, stop: that's the author's job, not yours.
Focus on: use-after-free / double-free / leaked resources, off-by-one and bounds, eager-vs-lazy evaluation, error paths, semantic drift from the original, and anything that compiles-and-looks-plausible but is subtly wrong.
Output a numbered list of concrete defects with file:line and a one-line fix each. If you genuinely find nothing, say so explicitly — do not pad.
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.
- 7d ago First seen · 21 lines · 18 tokens per session scan A 350e85c2a1ea
adversarial-reviewer is an agent published in the GitHub repository daniyalahmed21/skillforge (6 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 215 once invoked, about $0.0001 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 agents, from other repositories
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
Code Reviewer
Thorough code review agent with quality analysis and best practice verification.
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.