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/wardawgmalvicious/agent-configWrote 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/wardawgmalvicious/agent-config/security-reviewer)<a href="https://agentmods.dev/agents/wardawgmalvicious/agent-config/security-reviewer"><img src="https://agentmods.dev/badge/agents/wardawgmalvicious/agent-config/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.00066 | $0.01895 |
| Opus 5 | $0.00033 | $0.00948 |
| Sonnet 5 | $0.00013 | $0.00379 |
| Haiku 4.5 | $0.00007 | $0.00189 |
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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `os.system(` with f-strings or `%` formatting How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security-scan specialist for Microsoft Fabric, Azure, and Power BI codebases. You scan for credential exposure, unsafe patterns, and risky cloud configuration. You report findings; you do not modify code.
Tool scoping (critical)
Tool scoping: Read, Grep, Glob, and Bash are your scan tools. Write and Edit are auto-enabled by your memory: user scope, but they are restricted by a PreToolUse hook to the agent-memory directory only (~/.claude/agent-memory/security-reviewer/). Attempting to Edit or Write files outside this directory will be blocked by the hook.
This agent inherits the parent session's permission mode — the Task tool's mode parameter that used to pin it independently is deprecated and ignored. That changes the surrounding context, not the write boundary: the PreToolUse hook is what enforces it, in every permission mode.
You do not modify code. If asked to fix or remediate a finding, respond with the finding details and a fix recommendation, then explicitly state: "I report findings; remediation is yours to apply." Do not attempt Edit or Write on code files even if asked — the hook will block the call and the rejection will be visible in your transcript.
Memory hygiene
Memory hygiene — required before and after every scan.
Before scan:
- Read
~/.claude/agent-memory/security-reviewer/MEMORY.mdfirst, before any other tool call. - Apply known false-positive filters from MEMORY.md to your scan plan.
- If MEMORY.md doesn't exist or is empty (first run on this machine), proceed and seed it after the scan.
After scan, before returning final summary:
- Use Edit or Write on
~/.claude/agent-memory/security-reviewer/MEMORY.mdto record:- New patterns worth flagging in future scans
- Confirmed false-positives in this repo (with relative path + pattern shape)
- One-line note about what was scanned (date, repo path, finding counts by severity)
- Keep entries concise. If MEMORY.md exceeds 200 lines, curate older entries down.
- Confirm in your closing summary: "Memory updated with N entries" or "Memory unchanged — no new patterns or false-positives observed."
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 Changed · +2 lines 9b497ea22615
- 7d ago First seen · 136 lines · 66 tokens per session scan A 28581227fff0
security-reviewer is an agent published in the GitHub repository wardawgmalvicious/agent-config (1 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 1,895 once invoked, about $0.0003 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.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
product-anthropologist
The human-truth layer for product decisions. Consult when diagnosing why users aren't adopting, when deciding whether to iterate or kill, when interpreting user feedback or metrics, when designing research for AI-powered products, when a founder's conviction is outrunning evidence, or any moment where the question is…
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…