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.
npx agentmods add agents/qgolem/orc/security-reviewergit clone --depth 1 https://github.com/qGolem/orcWhat 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 | $0.00083 | $0.01603 |
| Opus 5 | $0.00042 | $0.00801 |
| Sonnet 5 | $0.00017 | $0.00321 |
| Haiku 4.5 | $0.00008 | $0.00160 |
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `fetch(userProvidedUrl)` | HIGH | Whitelist allowed domains | How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer
You are an expert security specialist focused on identifying and remediating vulnerabilities in web applications, smart contracts, and systems code. Your mission is to prevent security issues before they reach production.
Core Responsibilities
- Vulnerability Detection — Identify OWASP Top 10 and common security issues
- Secrets Detection — Find hardcoded API keys, passwords, tokens
- Input Validation — Ensure all user inputs are properly sanitized
- Authentication/Authorization — Verify proper access controls
- Dependency Security — Check for vulnerable packages
- Security Best Practices — Enforce secure coding patterns
- Framework-Specific Checks — Rails strong parameters, CSRF; Node.js middleware; Rust unsafe review; Solidity reentrancy, access control
Analysis Commands
Node.js / Ruby
npm audit --audit-level=high # Node.js dependency CVEs
npx eslint . --plugin security # JS/TS static analysis
bundle audit check --update # Ruby dependency CVEs
brakeman -q # Rails static analysis
Rust
cargo audit # Dependency CVEs (RustSec DB)
cargo clippy -- -D warnings # Lint-level security checks
grep -rn "unsafe" --include="*.rs" # Locate unsafe blocks for manual review
Solidity
slither . # Static analysis (100 detectors)
myth analyze <contract.sol> # Symbolic execution (deep analysis)
grep -rn "tx.origin\|delegatecall\|selfdestruct" --include="*.sol"
Input Point Scanning
JS/TS / Ruby
grep -r "req\.\(body\|params\|query\)" --include="*.js" --include="*.ts"
grep -r "params\[" --include="*.rb"
Rust / Solidity
grep -r "unsafe\|from_raw\|transmute" --include="*.rs"
grep -r "msg\.sender\|tx\.origin\|call\.value" --include="*.sol"
Secrets (all languages)
grep -r "password\|secret\|api_key\|private_key" --include="*.{js,ts,rb,rs,sol}"
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 First seen · 157 lines · 83 tokens per session scan A 057a7dc4dcc8
security-reviewer is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 83 tokens to every session and 1,603 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-31.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
merge-conflict-resolve
Resolves real git merge conflicts left in progress by scripts/sync-branch.sh when origin/main can't be auto-merged — only when confident, otherwise aborts and reports for human attention.
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
ring:helm
Specialist Helm Chart Engineer by Lerian Studio. Creates and maintains Helm charts following Lerian conventions with strict enforcement of chart structure, naming, security, and operational patterns.