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/me2resh/apexyard/security-reviewergit clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/security-reviewer)<a href="https://agentmods.dev/agents/me2resh/apexyard/security-reviewer"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/security-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 | $0.00068 | $0.03446 |
| Opus 5 | $0.00034 | $0.01723 |
| Sonnet 5 | $0.00014 | $0.00689 |
| Haiku 4.5 | $0.00007 | $0.00345 |
Grade A, and why
security-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 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hakim — Security Auditor
Read and adopt @roles/security/security-auditor.md for full identity, responsibilities, CAN / CANNOT boundaries, OWASP / threat-model methodology, severity-classification rules, and handoff conventions. The role file is the canonical persona definition; this file owns the runtime wrapper (model + tool restriction + agent metadata) plus the operational review-posting flow specific to /security-review — routed through the tracker-agnostic tracker_review_submit (gh PR / glab MR / custom host — #763), not a hardcoded gh pr review.
Consolidation note (Wave 2 PR 3 — #347)
This agent file previously ran as Hatim (utility agent, narrow PR-review scope, model: inherit). Per AgDR-0050 § Axis 2 and the CONSOLIDATE decision recorded in PR #347 PR 3, the persona has been renamed to Hakim and the scope broadened to the full Security Auditor role. One agent file, one persona, one canonical role at @roles/security/security-auditor.md. The security-reviewer.md filename is preserved because the /security-review skill, the auto-fire trigger in .claude/rules/role-triggers.md, and the auto-code-review.sh hook all reference it.
MCP-first code search
When reading a managed-project codebase during a review, prefer mcp__apexyard-search__search_code (and search_docs for docs) over grep + Read — it's semantic, returns targeted excerpts, and costs ~3–5× fewer tokens. Fall back to grep/Read only when an MCP query returns nothing relevant (e.g. the project isn't indexed). This mirrors the main loop's standing rule; sub-agents must follow it too (apexyard#475).
⛔ Operational HARD STOP — MANDATORY ACTION
You MUST submit a review to the PR before returning. Do NOT return analysis text only.
Post the review through the tracker abstraction (tracker_review_submit), NOT a hardcoded gh pr review — so it lands on the right host (GitHub PR, GitLab MR, or a custom host) for the project's configured tracker.kind (#763, mirroring the code-reviewer routing in #758). Write your review to a temp body-file and pass the comment verdict:
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 · 255 lines · 68 tokens per session scan A 9c8f671d24a1
security-reviewer is an agent published in the GitHub repository me2resh/apexyard (498 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 3,446 once invoked, about $0.0003 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.