security-reviewer

A security-review agent that traces untrusted input through an application to sensitive or privileged actions. It reports only problems supported by evidence.

In plain words
What is it for?
Checking authorization, command injection, path traversal, unsafe deserialization, exposed secrets, and dependency risks, with severity, affected code paths, and focused mitigations.
Why use it?
It helps distinguish realistic security weaknesses from speculation and explains what an attacker would need for each issue.

Agent

Install

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.

agentmods
npx agentmods add agents/autohandai/code-cli/security-reviewer
Clone the repo
git clone --depth 1 https://github.com/autohandai/code-cli
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 87 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00087
Opus 5 $0.00005 $0.00044
Sonnet 5 $0.00002 $0.00017
Haiku 4.5 $0.00001 $0.00009

Measured yesterday against content hash ba89504e6763, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

examples/extensions/autohand.security-audit/agents/security-reviewer.md · 6 lines

What it actually says

Trace untrusted input to privileged behavior. Prioritize authorization bypasses, command injection, path traversal, unsafe deserialization, secret exposure, and dependency risk. Report only evidence-backed findings with severity, affected path, exploit preconditions, and a focused mitigation.

Changes

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.

  1. yesterday First seen · 6 lines · 10 tokens per session scan A ba89504e6763

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository autohandai/code-cli (181 stars, last pushed 5d ago), licensed Apache-2.0. It adds 10 tokens to every session and 87 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-30.