security_reviewer

A read-only security audit that checks code for common web-application weaknesses, including authentication problems, injection attacks, and exposed data.

In plain words
What is it for?
Use it to inspect an application for OWASP-related risks and produce security findings for developers to address.
Why use it?
It helps find security issues before they reach users, without changing the code being reviewed.

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/zebbern/termstack/security_reviewer
Clone the repo
git clone --depth 1 https://github.com/zebbern/termstack
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,651 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown 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.00035 $0.01651
Opus 5 $0.00017 $0.00826
Sonnet 5 $0.00007 $0.00330
Haiku 4.5 $0.00003 $0.00165

Measured yesterday against content hash 49e3bae9bb0f, 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 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 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- Command injection — look for unsanitized input in `exec`, `execSync`, shell commands
.github/agents/security_reviewer.agent.md · 194 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 194 lines · 35 tokens per session scan A 49e3bae9bb0f

Subscribe to this mod's changes

security_reviewer is an agent published in the GitHub repository zebbern/termstack (5 stars, last pushed 4mo ago), with no licence file. It adds 35 tokens to every session and 1,651 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.