security-review

A security review workflow for features that handle sensitive operations such as sign-in, payments, administrator actions, user-data APIs, or files.

In plain words
What is it for?
Use it to review authentication, payment, administration, user-data API routes, and file operations for the security concerns relevant to each area.
Why use it?
It helps identify risks such as stolen sessions, unauthorized access, unsafe input, path traversal, and weak file controls before release.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/sequant-io/sequant/security-review
Any agent
npx skills add sequant-io/sequant --skill security-review
Clone the repo
git clone --depth 1 https://github.com/sequant-io/sequant

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,781 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.02781
Opus 5 $0.00011 $0.01391
Sonnet 5 $0.00004 $0.00556
Haiku 4.5 $0.00002 $0.00278

Measured 2d ago against content hash c54bdd849de3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.claude/skills/security-review/SKILL.md · 362 lines

How it starts

The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Local overrides (read this first). Before following any instruction below, check whether .claude/.local/skills/security-review/overrides.md exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor /security-review without forking it — overrides.md lives under .claude/.local/, which sequant update and sync never overwrite.

Security Review Command

You are the Security Review Agent for the current repository.

Purpose

When invoked as /security-review, perform a comprehensive security analysis focused on the specific security domain of the feature being implemented.

When to Use

Feature Type Use /security-review? Focus Areas
Auth flows Yes Session handling, token security, password hashing
Payment Yes PCI compliance, data handling, error messages
Admin features Yes Privilege escalation, IDOR, access control
API routes (user data) Yes Input validation, auth checks, rate limiting
File operations Yes Path traversal, file type validation, size limits
UI-only changes No Use /qa security checks
Content updates No No security surface

For lightweight security checks on every issue, use /qa instead.

Behavior

Invocation:

  • /security-review 123:
    • Treat 123 as the GitHub issue number.
    • Analyze the feature being implemented for that issue.
  • /security-review --domain auth:
    • Perform review focused on authentication domain.
  • /security-review --domain api:
    • Perform review focused on API security domain.
  • /security-review --domain admin:
    • Perform review focused on admin/authorization domain.

Process

1. Identify Security Domain

Analyze the feature being implemented to determine which security domain(s) apply:

Auto-detection signals:

  • Authentication: Issue mentions "login", "password", "session", "token", "auth", "logout"
  • Authorization: Files in app/admin/, mentions "role", "permission", "access control"
  • API Security: Files in app/api/, mentions "endpoint", "request", "validation"
  • Data Protection: Mentions "PII", "sensitive", "encrypt", "GDPR", "privacy"
  • Infrastructure: Mentions "env", "secret", "config", "headers", "CSP"
  • File Operations: Mentions "upload", "download", "file", "path"

Read the full file on GitHub · 362 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 2d ago First seen · 362 lines · 22 tokens per session scan A c54bdd849de3

Subscribe to this mod's changes

security-review is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 2,781 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

agent-estate

Perpetual autonomous work loop for Claude Code — no end condition, no memory regression, no context overfill. Maintains a persistent ledger across all sessions.

MercuriusDream/agent-estate · 36 tokens

paper-illustration

Generate publication-quality AI illustrations for academic papers using Gemini image generation. Creates architecture diagrams, method illustrations with Claude-supervised iterative refinement loop. Use when user says "生成图表", "画架构图", "AI绘图", "paper illustration", "generate diagram", or needs visual figures for papers.

wanshuiyin/Auto-claude-code-research-in-sleep · 67 tokens

mermaid-diagram

Generate Mermaid diagrams from user requirements. Supports flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, and 18 more diagram types.

wanshuiyin/Auto-claude-code-research-in-sleep · 36 tokens

experiment-plan

Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after research-refine, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty…

wanshuiyin/Auto-claude-code-research-in-sleep · 80 tokens

patent-novelty-check

Assess patent novelty and non-obviousness against prior art. Use when user says "专利查新", "patent novelty", "可专利性评估", "patentability check", or wants to evaluate if an invention is patentable.

wanshuiyin/Auto-claude-code-research-in-sleep · 59 tokens

overleaf-sync

Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…

wanshuiyin/Auto-claude-code-research-in-sleep · 97 tokens