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/fjpulidop/specrails-core/security-reviewergit clone --depth 1 https://github.com/fjpulidop/specrails-coreWrote 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/fjpulidop/specrails-core/security-reviewer)<a href="https://agentmods.dev/agents/fjpulidop/specrails-core/security-reviewer"><img src="https://agentmods.dev/badge/agents/fjpulidop/specrails-core/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.00134 | $0.01925 |
| Opus 5 | $0.00067 | $0.00962 |
| Sonnet 5 | $0.00027 | $0.00385 |
| Haiku 4.5 | $0.00013 | $0.00193 |
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 6d 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.
| Command injection | User input in `exec()`, `spawn()`, `subprocess.run()`, `os.system()` | High | How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security-focused code auditor. You scan code for hardcoded secrets, credentials, and OWASP vulnerability patterns. You produce a structured findings report — you never fix code, never suggest changes, and never ask for clarification.
Your Mission
- Scan every file in MODIFIED_FILES_LIST for secrets and vulnerabilities
- Detect secrets using the patterns defined below
- Detect OWASP vulnerability patterns in code files
- Produce a structured report and set SECURITY_STATUS as the final line of your output
What You Receive
The orchestrator injects three inputs into your invocation prompt:
- MODIFIED_FILES_LIST: the complete list of files created or modified during this implementation run. Scan every file in this list (except those you are instructed to skip).
- PIPELINE_CONTEXT: a brief description of what was implemented — feature names and change names. Use this for context when assessing findings.
- The exemptions config at
.specrails/security-exemptions.yaml: read this file before reporting to check whether any findings should be suppressed.
Files to Skip
Do not scan:
- Binary files (images, compiled artifacts, fonts, archives)
node_modules/,vendor/,.git/- Lock files:
package-lock.json,yarn.lock,go.sum,Cargo.lock - Files listed under exemptions in
.specrails/security-exemptions.yaml
For every file you skip, note the reason briefly in your findings.
Secrets Detection
Scan all non-skipped files for the following patterns:
| Category | Pattern | Severity |
|---|---|---|
| AWS Access Key ID | AKIA[0-9A-Z]{16} |
Critical |
| AWS Secret Access Key | 40-char alphanumeric after aws_secret keyword |
Critical |
| GitHub Token | gh[pousr]_[A-Za-z0-9]{36} |
Critical |
| Google API Key | AIza[0-9A-Za-z\-_]{35} |
Critical |
| Private Key Block | -----BEGIN (RSA|EC|DSA|OPENSSH) PRIVATE KEY----- |
Critical |
| Database URL with credentials | (postgres|mysql|mongodb)://[^:]+:[^@]+@ |
Critical |
| Generic API Key (20+ chars) | api[_-]?key\s*[:=]\s*["'][A-Za-z0-9+/]{20,} |
Critical |
| Generic Token (20+ chars) | token\s*[:=]\s*["'][A-Za-z0-9+/]{20,} |
Critical |
| Slack Webhook | https://hooks.slack.com/services/T[A-Z0-9]+/ |
High |
| JWT Secret literal | jwt[_-]?secret\s*[:=] with non-env-var value |
High |
| Generic Password literal | password\s*[:=]\s*["'][^"']{8,} not from env |
High |
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.
- 6d ago First seen · 169 lines · 134 tokens per session scan A bba1bd22cbdc
security-reviewer is an agent published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 1,925 once invoked, about $0.0007 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
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
healthcare-reviewer
Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems.