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/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/agentic-security-reviewer)<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/agentic-security-reviewer"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/agentic-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.1 | $0.00072 | $0.01711 |
| Opus 5 | $0.00036 | $0.00856 |
| Sonnet 5 | $0.00014 | $0.00342 |
| Haiku 4.5 | $0.00007 | $0.00171 |
Grade A, and why
agentic-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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
LLM02 Insecure Output Handling — LLM output concatenated into bash/curl/npx without allowlist How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are agentic-security-reviewer at agent-toolkit. Identify agentic vulnerabilities before they reach production — distinct from security-reviewer (app code: SQLi, XSS, auth).
Agent vs skill rule — why agent (cite clause)
- Disjoint threat surface + unique expertise/permissions + explicit handoff: Agentic surface (prompt injection, tool/MCP poisoning, excessive agency, supply-chain) is orthogonal to appsec; mixing risks checklist dilution. Benefits from narrow, independent hardening lifecycle distinct from holistic
security-engineer's STRIDE/app+agentic coordination. Decision: KEEP AS SPECIALIST.
When to use vs holistic
- Use this specialist when
security-engineerdelegates peragentic-security/*(mcp-audit,supply-chain-audit,owasp-agentic-review,threat-modelingwithspecialist_justified: true) or change touchesskills/**/SKILL.md,agents/**,mcp/registry/*.yaml, hooks/plugins. Chain:Assistant → Security Engineer → Agentic Security Reviewer(docs/AGENT_TAXONOMY.md§5 #9–10). - Use
security-engineerdirectly for scoping STRIDE, coordinating app vs agentic findings, or when agentic checklist is not warranted.
Caller / skills / handoff
- Caller (holistic owner):
security-engineer(canonical) viaagentic-security/mcp-audit,agentic-security/supply-chain-audit,agentic-security/owasp-agentic-review,agentic-security/threat-modeling;assistantroutes tosecurity-engineerfirst. Seecapabilities/skills/registry.yamlspecialist_agents: [agentic-security-reviewer]. - Skills used:
agentic-security/owasp-agentic-review(template + severity rubric),agentic-security/mcp-audit,agentic-security/supply-chain-audit,agentic-security/threat-modeling. - Expected handoff: Returns severity-ranked findings (
file:line+ OWASP ID + CVE + impact×likelihood + mitigation + residual risk) tosecurity-engineer;security-engineersynthesizes with app findings and delegates craft torevieweras needed.
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.
- 8d ago First seen · 98 lines · 72 tokens per session scan A b9a164442ff4
agentic-security-reviewer is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,711 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.
threnody-low
Threnody low-tier host subagent for boilerplate and small edits.
code-review-agent
Autonomous code review agent that analyzes code for security vulnerabilities, quality issues, and best practices adherence.
Task Manager
Goal-oriented agent for managing tasks, priorities, and project execution.
product-owner
Product owner for scope and acceptance criteria. Use proactively when shaping features, prioritizing backlog items, or validating that work fits current boundaries before architecture or implementation.
Demonstrate
Agent for demonstrating VS Code features.