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 Security-Phoenix-demo/security-skills-claude-code --skill security-reviewergit clone --depth 1 https://github.com/Security-Phoenix-demo/security-skills-claude-codeWrote 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/security-phoenix-demo/security-skills-claude-code/security-reviewer)<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/security-reviewer"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/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/skills/security-phoenix-demo/security-skills-claude-code/security-reviewer"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/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.00185 | $0.01342 |
| Opus 5 | $0.00093 | $0.00671 |
| Sonnet 5 | $0.00037 | $0.00268 |
| Haiku 4.5 | $0.00018 | $0.00134 |
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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- security-reviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer
A pragmatic AppSec review pass for any modern stack. Output is short, severity-ranked findings with file paths, evidence, and a concrete fix — never a 30-page "report".
When to run
Run on any of:
- New HTTP route, RPC handler, or queue consumer
- Auth, session, RBAC, or tenant-isolation change
- Frontend rendering / templating change (XSS surface)
- Outbound HTTP, file fetch, or URL handling (SSRF surface)
- Database query change (injection / IDOR surface)
- Dependency manifest change or lockfile bump
- Config / IaC change (CORS, headers, CSP, IAM, secrets)
- End of a major feature, pre-release, or before opening a PR labelled
security-sensitive
If unsure, run it. False positives are cheap; missed CVEs are not.
Eight-point check (language-agnostic)
These eight categories drive every review. Every finding maps to one.
- Authn/Authz — every route has explicit auth + role/tenant checks; no implicit "logged-in means allowed"
- Output encoding — all user-influenced HTML/markdown/JSON/log output is encoded for its sink
- SSRF & outbound HTTP — URL allow-listed, redirects bounded, IMDS / link-local / RFC1918 blocked unless intentional
- Secrets & key material — no client-side storage, no hardcoded keys, no secrets in URLs or logs
- Input handling — parameterised queries, path containment, redirect target validation, deserialisation guards
- Config & headers — CSP, HSTS, X-Content-Type-Options, secure cookies, CORS allowlist, rate limits, dev-bypass off in prod
- Supply chain — dependencies pinned, lockfile committed, manifest scanned, no unknown registries, install scripts reviewed
- Failure modes — fail-closed on auth/policy errors, no broad
except/catch, errors don't leak stack traces or PII
Routing
When language is known, load the matching reference and use its diagnostic patterns. When mixed, run all relevant ones.
| Detected from… | Read… |
|---|---|
pyproject.toml, requirements*.txt, Pipfile, setup.py |
languages/python.md |
package.json, *.ts, *.tsx, *.js, *.jsx |
languages/javascript-typescript.md |
go.mod |
languages/go.md |
Cargo.toml |
languages/rust.md |
pom.xml, build.gradle*, *.kt, *.java |
languages/java.md |
Gemfile, *.rb |
languages/ruby.md |
*.csproj, *.sln, *.cs |
languages/dotnet.md |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 88 lines · 185 tokens per session scan A fc77a15b8f0c
security-reviewer is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed 4mo ago), licensed MIT. It adds 185 tokens to every session and 1,342 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…