security-scan

security-scan is a skill for Claude Code from davila7/claude-with-skills. It costs 52 tokens per session (787 once invoked), scanned A, original, MIT.

A code review procedure that searches a project for common security problems, such as exposed passwords, unsafe database queries, cross-site scripting, unchecked input, and insecure defaults.

In plain words
What is it for?
Use it before deploying, during a code-quality review, or when checking a codebase for common security issues.
Why use it?
It helps reveal risks in changed or existing code before release or deployment.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

Good fit Use it before deploying, during a code-quality review, or when checking a codebase for common security issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davila7/claude-with-skills/security-scan
About the project

Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.

davila7/claude-with-skills · 11 stars · on GitHub · claude-with-skills.vercel.app

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.

Any agent
npx skills add davila7/claude-with-skills --skill security-scan
Clone the repo
git clone --depth 1 https://github.com/davila7/claude-with-skills

Made for: Claude Code.

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/davila7/claude-with-skills/security-scan/github.svg)](https://agentmods.dev/skills/davila7/claude-with-skills/security-scan)
Your own site
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/security-scan"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/security-scan/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.

agentmods 80×15 button for security-scan

Your own site · 80×15
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/security-scan"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 787 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00052 $0.00787
Opus 5 $0.00026 $0.00394
Sonnet 5 $0.00010 $0.00157
Haiku 4.5 $0.00005 $0.00079

Measured 10d ago against content hash e1b5c5a8650b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 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.

src/content/docs/03-advanced/capstone/solution/.claude/skills/security-scan/SKILL.md · 72 lines

How it starts

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

Run a security scan on this codebase.

Changed files (focus here first)

!git diff --name-only HEAD~1 2>/dev/null || git diff --name-only origin/main...HEAD 2>/dev/null || echo "all files — no git diff available"

Prioritize scanning the files listed above. If the output says "all files", scan the entire codebase.

Security checks

For each check, search the changed files first. If changed files is "all files", search the entire codebase excluding node_modules/, dist/, .git/, vendor/, and *.min.js.

1. Hardcoded secrets

Search for patterns like password=, api_key=, secret=, token=, passwd=, private_key= followed by a literal value (not a variable reference or environment variable lookup).

Exclude:

  • Files in test/, spec/, __tests__/ directories
  • Files ending in .example, .sample, .template
  • Lines that contain process.env, os.environ, getenv, ${, $(, or config.get

2. SQL injection risk

Search for SQL keywords (SELECT, INSERT, UPDATE, DELETE, WHERE, FROM) appearing inside f-strings (Python), template literals (JavaScript/TypeScript), or string concatenation patterns where a variable is embedded directly. Look for patterns like:

  • f"SELECT ... {variable}
  • `SELECT ... ${variable}`
  • "SELECT " + variable

3. XSS vectors

Search .js and .ts files for innerHTML being assigned a value that includes a variable: element.innerHTML = , .innerHTML +=. Flag any assignment that does not call a sanitization function (DOMPurify.sanitize, sanitize(, escapeHtml().

4. Unvalidated inputs

Search for patterns where request body or parameters are passed directly to a database function without an intervening validation step. Look for req.body., request.data, request.form, params[ in close proximity (within 5 lines) to database calls (query(, execute(, find(, .save(, .create().

5. Insecure defaults

Search for:

  • DEBUG = True or DEBUG=True (Python)
  • NODE_ENV not set to production in deployment configuration files
  • verify=False in Python requests calls
  • CORS configured to allow all origins: cors({ origin: '*' }), Access-Control-Allow-Origin: * in non-development config files

Read the full file on GitHub · 72 lines

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. 10d ago First seen · 72 lines · 52 tokens per session scan A e1b5c5a8650b

Subscribe to this mod's changes

security-scan is a skill published in the GitHub repository davila7/claude-with-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 787 once invoked, about $0.0003 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.