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/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/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/me2resh/apexyard/security-reviewer"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/security-reviewer.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.00068 | $0.06317 |
| Opus 5.5 | $0.00027 | $0.02527 |
| Sonnet 5.5 | $0.00014 | $0.01263 |
| Haiku 4.5 | $0.00007 | $0.00632 |
Grade A, and why
security-reviewer scanned grade A with 1 finding 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 15d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
8. **A re-review is a delta re-review by default** — read only the commits since your last reviewed SHA, per § "Delta Re-Reviews". Read CI's own check-run result for the head SHA before running a test or probe yourself, Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 357 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.
Writing standard
Before you write a durable artifact, read .claude/rules/writing-standard.md.
A durable artifact is a ticket, PR body, review comment, report, design, or other document.
Use the controlled technical writing profile in that rule.
The rule does not apply to chat replies.
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.
Code search
Use grep and Read when you read a managed-project codebase.
Do the complete read. Do not skip or shorten the step.
⛔ 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 the review body with the Write tool to $REVIEW_BODY_FILE. That is the sanctioned body path that review_body_path returns: <ops-root>/.claude/session/reviews/bodies/<owner>__<repo>__{number}-security.md. Then pass that file and the comment verdict to tracker_review_submit (me2resh/apexyard#1840, AgDR-0266). Do not write the body with a Bash heredoc. The Bash gates read quoted command text in a heredoc as commands, and they block the write. Each review round on one PR uses the same body path. When the file exists from an earlier round, read it with the Read tool first, then replace it with the Write tool.
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.
- 15d ago Changed · +26 lines 8c4a98518e5f
- 22d ago Changed · +2 lines f6f99dc78e67
- 29d ago Changed · -9 lines 804075d83f5b
- 1mo ago Changed · +79 lines f3174bd179d5
- 1mo ago Changed · +4 lines 905eb4a227a3
- 2mo ago First seen · 255 lines · 68 tokens per session scan A 9c8f671d24a1
security-reviewer is an agent published in the GitHub repository me2resh/apexyard (542 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 6,317 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
security-reviewer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| security-reviewerme2resh/apexyard | Agent | 542 | yesterday | MIT | A | 68 | Claude Code |
| project-auditoravelikiy/great_cto | Agent | 112 | 2d ago | MIT | A | 41 | Claude Code |
| design-advisoravelikiy/great_cto | Agent | 112 | 2d ago | MIT | A | 86 | Claude Code |
| insurance-revieweravelikiy/great_cto | Agent | 112 | 2d ago | MIT | A | 153 | Claude Code |
| smart-contract-auditoravelikiy/great_cto | Agent | 112 | 2d ago | MIT | A | 108 | Claude Code |
| accounting-revieweravelikiy/great_cto | Agent | 112 | 2d ago | MIT | A | 52 | Claude Code |
| ai-eval-engineeravelikiy/great_cto | Agent | 112 | 2d ago | MIT | A | 71 | Claude Code |