security-scan

security-scan is a skill for Claude Code, Codex from byerlikaya/claude-starter-kit. It costs 54 tokens per session (1,669 once invoked), scanned A, original, MIT.

A security audit method that traces untrusted input from its source to sensitive operations, while also checking dependencies and configuration. It works across programming languages and frameworks and ranks findings by severity.

In plain words
What is it for?
Use it when changing authentication, input handling, secrets, dependencies, or configuration, and before releasing a system.
Why use it?
It focuses review on weaknesses where attacker-controlled data can reach a dangerous operation without adequate checks. This helps identify security problems before they reach a release.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Claude Code.

Good fit Use it when changing authentication, input handling, secrets, dependencies, or configuration, and before releasing a system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/byerlikaya/claude-starter-kit/security-scan
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 byerlikaya/claude-starter-kit --skill security-scan
Clone the repo
git clone --depth 1 https://github.com/byerlikaya/claude-starter-kit

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/byerlikaya/claude-starter-kit/security-scan/github.svg)](https://agentmods.dev/skills/byerlikaya/claude-starter-kit/security-scan)
Your own site
<a href="https://agentmods.dev/skills/byerlikaya/claude-starter-kit/security-scan"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/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/byerlikaya/claude-starter-kit/security-scan"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,669 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.00054 $0.01669
Opus 5.5 $0.00022 $0.00668
Sonnet 5.5 $0.00011 $0.00334
Haiku 4.5 $0.00005 $0.00167

Measured 1mo ago against content hash 9569d865469f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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-starter/skills/security-scan/SKILL.md · 102 lines

How it starts

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

Security Scan

Trigger phrases: "security scan", "run a security scan", "OWASP check", "scan for vulnerabilities", "find security vulnerabilities", "security audit", "api key", "secret key", "leaked credential", "credentials leaked", "hardcoded secret", "hardcoded password", "sql injection", "can an attacker"

The core of a security vulnerability fits in a single sentence: an untrusted input reaches a dangerous operation without being adequately checked. This skill chases exactly that sentence — it first looks for where the input comes from, then where it flows, and what gate should sit in between. It is stack-agnostic: whatever the language/framework, the same logic applies; when current tooling and patterns are needed, it runs a web search.

Kit adaptation (local, .claude/): security-expert-csk applies this; findings are carried to review-agent-csk in severity order. It also holds for the default stack (.NET/PostgreSQL). Automatic fixes only with explicit approval (§4.4); .claude does not go to the repo (§4.3). §4 Prohibitions apply.

What it does, what it doesn't

  • Does: surfaces common vulnerability classes, known vulnerable dependencies, and risky configuration; ties each finding to a concrete fix.
  • Doesn't: does not replace a professional pentest / SAST / DAST. The report guides, it does not give full assurance — state this at the end of the report.
  • Boundary: analysis is local; code/data is not sent to an external service, and the project directory is not left.

A question is not a scan

Loading this skill does not mean running all of it. "Is this query injectable?", "should this key be in the repo?", "how do I hash these passwords?" are questions: answer them from the relevant part of this skill and stop — no discovery pass, no fan-out of verifiers, no coverage ledger, no report file. The full workflow below runs when the user asks for a scan, an audit or a security review of a codebase or a change, or asks for the report itself. When a request could be either, ask one question before starting the full workflow; do not guess upward.

Read the full file on GitHub · 102 lines

Files

What ships with it

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

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. 1mo ago Changed · +13 lines 9569d865469f
  2. 1mo ago First seen · 89 lines · 54 tokens per session scan A d9b131725a23

Subscribe to this mod's changes

security-scan is a skill published in the GitHub repository byerlikaya/claude-starter-kit (24 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,669 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories