security-scan

security-scan is a skill for Claude Code, Codex from forest6511/claude-code-recipes-v2. It costs 24 tokens per session (192 once invoked), scanned A, original, MIT.

A security review for a codebase or selected files. It checks for injection risks, authentication and permission problems, exposed secrets, and dependencies with known vulnerabilities.

In plain words
What is it for?
Use it to scan the whole source directory by default or a specified target. It is suited to reviewing SQL, command, and cross-site-scripting risks, access control, secrets, and dependency security.
Why use it?
It helps identify common ways an application could be attacked or leak sensitive information. Findings are tied to a file and line and include a suggested remedy.

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/forest6511/claude-code-recipes-v2/security-scan
Any agent
npx skills add forest6511/claude-code-recipes-v2 --skill security-scan
Clone the repo
git clone --depth 1 https://github.com/forest6511/claude-code-recipes-v2

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for security-scan

README.md
[![agentmods](https://agentmods.dev/badge/skills/forest6511/claude-code-recipes-v2/security-scan.svg)](https://agentmods.dev/skills/forest6511/claude-code-recipes-v2/security-scan)
Your own site
<a href="https://agentmods.dev/skills/forest6511/claude-code-recipes-v2/security-scan"><img src="https://agentmods.dev/badge/skills/forest6511/claude-code-recipes-v2/security-scan.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 192 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.00024 $0.00192
Opus 5 $0.00012 $0.00096
Sonnet 5 $0.00005 $0.00038
Haiku 4.5 $0.00002 $0.00019

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

Security

Grade A, and why

security-scan 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 5d 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.

ch07-skills-basics/recipe-38/.claude/skills/security-scan/SKILL.md · 21 lines

What it actually says

以下の対象に対してセキュリティ監査を実施してください。

対象: $ARGUMENTS(未指定の場合は src/ 配下全体)

チェック項目

  1. インジェクション (SQL / コマンド / XSS)
  2. 認証・認可の不備
  3. 機密情報のハードコード・ログ出力
  4. 既知の脆弱性を含む依存関係

出力形式

重要度ごとに「ファイル:行番号 -> 問題 -> 推奨対策」の3点セットで列挙してください。

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. 5d ago First seen · 21 lines · 24 tokens per session scan A 4cd8b2204e34

Subscribe to this mod's changes

security-scan is a skill published in the GitHub repository forest6511/claude-code-recipes-v2 (5 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 192 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens