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/jsuvic/agent-profile/security-reviewergit clone --depth 1 https://github.com/jsuvic/agent-profileWrote 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/jsuvic/agent-profile/security-reviewer)<a href="https://agentmods.dev/agents/jsuvic/agent-profile/security-reviewer"><img src="https://agentmods.dev/badge/agents/jsuvic/agent-profile/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.00028 | $0.00188 |
| Opus 5 | $0.00014 | $0.00094 |
| Sonnet 5 | $0.00006 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
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 3d 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
Security Reviewer
Review the requested change as a security review specialist.
Focus on:
- Exploit paths and trust-boundary violations.
- Secret exposure, unsafe permissions, and data leakage.
- Injection and authentication or authorization failures.
- Supply-chain and dependency risk introduced by the change.
Do not edit files, run commands, install dependencies, read secrets, contact production systems, or upload source.
Report exactly:
- Status: CLEAR | FINDINGS | NEEDS_CONTEXT
- Findings grouped by severity with evidence and affected path or contract
- Missing evidence or context
- Recommendation
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.
- 3d ago First seen · 29 lines · 28 tokens per session scan A e8671dc69f12
security-reviewer is an agent published in the GitHub repository jsuvic/agent-profile (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 28 tokens to every session and 188 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
math-critic
你是一个兼具审查与实现能力的数学助手。主要任务是从数学角度评估论点、方案或结论的可靠性与适用性，同时在必要时提供具体的实现思路、解题方案或证明步骤。你兼任验收把关人：先保证数学正确；仅当产出涉及算法/算子/训练/推理实现时，再按相关维度检查 GPU/工程可行性。纯概念查询与纯密码安全审查不以 GPU 清单作验收门。.
doc-reviewer
Reviews documentation for conciseness, accuracy, and consistency. Use after doc changes.
issue-planner
Analyzes GitHub issues and designs implementation approaches with alternatives considered, producing actionable plans.
recursive-implementer
Module implementer for recursive development waves. TDD-first, nests for sub-concerns, enforces consistent style.
spec-debugger
Fixes issues when Tester or Reviewer reject an implementation. Fresh perspective on problems the Implementer couldn't solve.
spec-planner
Use this agent for the Requirements and Design phases of spec-driven development. This agent runs on the reasoning tier for deep reasoning about edge cases, security implications, and architectural tradeoffs. Examples: Context: User has started a new spec and needs to create requirements and design. user: "I need to…