security-audit

security-audit is a skill for Claude Code from kimon1230/claude_extensions. It costs 31 tokens per session (8,950 once invoked), scanned B, original, MIT.

A structured review of source code, files, folders, or recent changes for security problems before release. It focuses on finding weaknesses in the parts of a project that handle requests, authentication, data, and configuration.

In plain words
What is it for?
Use it to review a codebase, a specific directory or file, or the differences in recent Git changes for security issues.
Why use it?
It helps identify security risks that ordinary testing or code review may miss. The review scope must be specified, such as selected files, recent changes, or the whole project.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions subagents; built for aider.

Good fit Use it to review a codebase, a specific directory or file, or the differences in recent Git changes for security issues.

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

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-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/kimon1230/claude_extensions/security-audit.svg)](https://agentmods.dev/skills/kimon1230/claude_extensions/security-audit)
Your own site
<a href="https://agentmods.dev/skills/kimon1230/claude_extensions/security-audit"><img src="https://agentmods.dev/badge/skills/kimon1230/claude_extensions/security-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,950 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00031 $0.08950
Opus 5 $0.00015 $0.04475
Sonnet 5 $0.00006 $0.01790
Haiku 4.5 $0.00003 $0.00895

Measured 7d ago against content hash 1cc336516a9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade B, and why

security-audit scanned grade B with 2 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 7d 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.

Cloud metadata endpointmediumServer-side request forgery

One request to 169.254.169.254 can return temporary IAM credentials.

- **SSRF bypass techniques**: Check that SSRF protections account for: decimal IP (`2130706433` = 127.0.0.1), octal IP (`0177.0.0.1`), hex IP (`0x7f.0x0.0x0.0x1`), IPv6 localhost (`[::1]`), IPv4-mapped IPv6 (`[::ffff:127

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `parse_url()` vs curl parsing discrepancy: double-`@` in URLs parsed differently, enabling SSRF bypass
skills/security-audit/SKILL.md · 340 lines

How it starts

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

Security Review

This skill must only be invoked from the main session, never from a subagent.

1. Determine Scope

a. If the user specified file paths, directories, or a description of what to review, use that as the scope. b. If the user said "review my changes" or similar, use git diff HEAD (unstaged + staged) and git diff --cached as the scope. If no changes exist, tell the user and stop. c. If no scope is specified, ask the user: "What should I review? Options: specific files/directories, recent changes (git diff), or the entire project." d. For entire-project scope, identify all source files (exclude vendored/generated code, build artifacts, lock files, and test fixtures). Prioritize by security relevance: route definitions, API handlers, middleware, auth modules, database access layers, and configuration files. Distribute files across agents by relevance to each agent's domain. e. Confirm scope with the user before proceeding: "I'll security-review [scope description]. Correct?"

Web Application Detection

After determining scope, check whether the project is a web application by looking for indicators: route/endpoint definitions, HTTP framework imports (Express, Flask, Django, FastAPI, Spring, Next.js, Rails, ASP.NET, etc.), HTML templates, API handlers, or middleware. If detected, set web_app = true and inform the user: "Detected web application — enabling web-specific security checks (Agent 6)." If uncertain, ask.

Threat Context

Before spawning subagents, build a threat context by examining at most 10 files (entry points, configs, auth modules, route definitions):

  • Trust boundaries: Where untrusted input enters (user input, external APIs, file uploads, webhooks, message queues) and where it's consumed (database, command execution, rendering, serialization).
  • Data sensitivity: Classify data handled — PII, financial, health/PHI, authentication material, or public-only. Note the highest sensitivity tier.
  • High-risk components: Identify the 3-5 components with most exposure: auth modules, payment processing, admin endpoints, data export/import, file handling, external integrations.

Read the full file on GitHub · 340 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. 7d ago First seen · 340 lines · 31 tokens per session scan B 1cc336516a9d

Subscribe to this mod's changes

security-audit is a skill published in the GitHub repository kimon1230/claude_extensions (4 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 8,950 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (cloud metadata endpoint, makes network calls). 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

prompt-sensei

Stage-aware prompt coaching, prompt improvement, lookback analysis, prompting habit feedback, and local reports about prompt quality for AI coding agents such as Claude Code or Codex.

chengzhongwei/Prompt-sensei · 39 tokens

nil

The inverse of /sfl. Where sfl saved each window for later, /nil says later is now: it reopens them. You choose which to bring back.

wasulajr/headsup · 153 tokens

headsup-config

Unified settings hub for headsup (Claude Code's iTerm2 status hooks). One command with a section as the first word, then that section's args. Sections: newtabs (New Claude Tab / Cmd-Opt-C launch mode), colors (idle/processing/waiting tab colors), label (this tab's title + badge), notify (the 'Claude is waiting' macOS…

wasulajr/headsup · 153 tokens

sfl

Save For Later: checkpoint this window so a fresh session (or /nil) can resume it later. Use when the user types /sfl, "save for later", or "checkpoint this window". Writes a live per-window entry under /.claude/sfl/ (plus an optional durable note in the user's own memory system), then shows the green Saved-for-Later…

wasulajr/headsup · 121 tokens

headsup

Show the default headsup health/status snapshot for Claude Code tabs. Use when the user types /headsup, asks whether headsup is working, or wants the quick overview rather than a specific focused command. For focused actions, route to /headsup-label, /headsup-config, /headsup-status, /headsup-diagnose…

wasulajr/headsup · 90 tokens

headsup-colors

Customize headsup's global iTerm2 tab colors for Codex sessions: idle, working, and waiting. Use when the user asks to change Codex/headsup tab colors.

wasulajr/headsup · 41 tokens