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 skills add selmakcby/claude-agents-skills --skill security-reviewgit clone --depth 1 https://github.com/selmakcby/claude-agents-skillsWrote 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/skills/selmakcby/claude-agents-skills/security-review)<a href="https://agentmods.dev/skills/selmakcby/claude-agents-skills/security-review"><img src="https://agentmods.dev/badge/skills/selmakcby/claude-agents-skills/security-review/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/skills/selmakcby/claude-agents-skills/security-review"><img src="https://agentmods.dev/badge/skills/selmakcby/claude-agents-skills/security-review.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.00045 | $0.00892 |
| Opus 5 | $0.00023 | $0.00446 |
| Sonnet 5 | $0.00009 | $0.00178 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
security-review 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
When to trigger
- After writing code touching auth, payments, API endpoints, file I/O, or user input
- Before commit on security-sensitive changes
- When user asks
/security-review
Scanning mode
Diff-aware: only analyze changed files in the current PR/commit. Focus on real vulnerabilities — filter out false positives aggressively.
What to check (OWASP Top 10 mapping)
1. Injection
- SQL injection → parameterized queries?
- NoSQL injection → $where clauses, user-controlled operators?
- Command injection →
exec()with user input? - Prompt injection (AI-specific) → user input flowing into system prompts?
2. Broken authentication
- Missing auth checks on protected routes
- Weak password hashing (bcrypt/argon2 required)
- JWT misuse — missing signature verification, weak secrets,
nonealgorithm accepted - Session fixation, missing session rotation on login
3. Sensitive data exposure
- Hardcoded secrets in code
- API keys in client bundles (import in
"use client"components) - PII in logs
- Missing HTTPS enforcement
- Secrets in error messages
4. XML/XXE
- XML parsers with external entity processing enabled
5. Broken access control
- Missing authorization (authenticated but not authorized)
- IDOR (accessing other users' data by changing an ID)
- Privilege escalation paths
6. Security misconfiguration
- Default credentials
- Debug endpoints exposed in prod
- Missing security headers (CSP, HSTS, X-Frame-Options)
7. XSS
dangerouslySetInnerHTMLwith user input- Rendering LLM output without sanitization
- URL parameters reflected without escaping
8. Insecure deserialization
JSON.parsewith user-controlled content (usually fine in JS, but watch for prototype pollution)
9. Using components with known vulnerabilities
- Run
npm auditmentally — are any flagged deps in critical paths?
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.
- 12d ago First seen · 110 lines · 45 tokens per session scan A 4880c5168226
security-review is a skill published in the GitHub repository selmakcby/claude-agents-skills (124 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 892 once invoked, about $0.0002 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-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…