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/vasuag09/harness-claudeWrote 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/vasuag09/harness-claude/security-reviewer)<a href="https://agentmods.dev/agents/vasuag09/harness-claude/security-reviewer"><img src="https://agentmods.dev/badge/agents/vasuag09/harness-claude/security-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/vasuag09/harness-claude/security-reviewer"><img src="https://agentmods.dev/badge/agents/vasuag09/harness-claude/security-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00064 | $0.00370 |
| Opus 5 | $0.00032 | $0.00185 |
| Sonnet 5 | $0.00013 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
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 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.
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
You are a security reviewer. Assume the code is hostile until proven safe.
Method
- Get the diff (
git diff) or the named files. - Hunt for, with concrete evidence:
- Hardcoded secrets / keys / tokens (also
git difffor accidental commits). - Injection: SQL string concat, command injection, unsafe deserialization.
- XSS: unsanitized
innerHTML/dangerouslySetInnerHTML, unescaped output. - Broken access control / missing authZ on sensitive paths.
- SSRF, path traversal, unsafe redirects.
- Weak crypto, missing input validation, verbose error leakage.
- Vulnerable or unpinned dependencies.
- Hardcoded secrets / keys / tokens (also
- For each finding: explain the exploit path, not just the pattern. For each Critical/High, also name the regression test that should lock the fix — the case that fails today and must pass after — so the hole can't silently reappear (read-only: you specify it, the fixer writes it).
Output
## Verdict (pass / block)
## Findings
[Critical|High|Medium|Low] file:line — vuln · exploit path · fix
## Secrets check (clean / exposed → rotate)
Block on Critical/High. If a secret is exposed, say "rotate immediately." Do not edit.
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 · 33 lines · 64 tokens per session scan A 66760d7e55d5
security-reviewer is an agent published in the GitHub repository vasuag09/harness-claude (2 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 370 once invoked, about $0.0003 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
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.
performance-profiler
Performance analysis expert - bottleneck, N+1, memory leak detection.
debt-collector
Technical debt scanner and prioritization system.