A security-audit command for checking an application against common web security risks, including the OWASP Top 10 list. It includes checks for secrets, dependencies, configuration, authentication, and attack surfaces.

Use it for a full audit or focused checks of secrets and dependencies, authentication, OWASP risks, or the application’s attack surface.

It helps find weaknesses such as exposed credentials, unsafe dependencies, broken access controls, and insecure settings before they are exploited.

How bugrabilge/bilge-development-kit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bugrabilge/bilge-development-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bugrabilge/bilge-development-kit/main/.claude/skills/security/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bugrabilge/bilge-development-kit

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/security/github.svg)](https://agentmods.dev/skills/bugrabilge/bilge-development-kit/security)

Your own site

<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/security"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/security/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/security"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 781 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.

Model	Per session	Once invoked
Fable 5.1	$0.00048	$0.00781
Opus 5.5	$0.00019	$0.00312
Sonnet 5.5	$0.00010	$0.00156
Haiku 4.5	$0.00005	$0.00078

Measured 2mo ago against content hash a86e82f811fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security 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 2mo 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/SKILL.md · 134 lines

How it starts

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

/security - Security Audit

$ARGUMENTS

Purpose

This command performs a comprehensive security audit on the project using security-auditor and penetration-tester agents.

Sub-commands

/security              - Full security audit
/security quick        - Quick scan (secrets + dependencies only)
/security auth         - Authentication/authorization review
/security deps         - Dependency vulnerability scan
/security owasp        - OWASP Top 10 checklist review

Behavior

When /security is triggered:

Automated scans

# Run security scan script
python .agent/skills/vulnerability-scanner/scripts/security_scan.py .

# Run dependency analysis
python .agent/skills/vulnerability-scanner/scripts/dependency_analyzer.py .

# Check for secrets in code
# (included in security_scan.py)

Agent analysis
- Invoke security-auditor agent for code review
- Invoke penetration-tester agent for attack surface analysis

OWASP Top 10:2025 checklist

#	Category	Check
A01	Broken Access Control	IDOR, auth bypass, SSRF
A02	Security Misconfiguration	Headers, CORS, defaults
A03	Supply Chain	Dependencies, lock files
A04	Cryptographic Failures	Weak crypto, exposed secrets
A05	Injection	SQL, XSS, command injection
A06	Insecure Design	Architecture flaws
A07	Auth Failures	Session, MFA, credentials
A08	Integrity Failures	Unsigned updates
A09	Logging Failures	Missing audit trails
A10	Exceptional Conditions	Error handling, fail-open

Generate report

Output Format

## Security Audit Report

### Scan Results
- Security Scan: PASS/FAIL
- Dependency Audit: X vulnerabilities (Y critical)
- Secrets Check: PASS/FAIL

### Findings by OWASP Category

#### A01: Broken Access Control
- [Finding or "No issues found"]

#### A05: Injection
- [Finding or "No issues found"]

[... all categories ...]

### Risk Summary
| Severity | Count | Action |
|----------|-------|--------|
| Critical | X | Fix immediately |
| High     | X | Fix before deploy |
| Medium   | X | Schedule fix |
| Low      | X | Document |

### Recommendations
1. [Priority fix with details]
2. [Secondary fix]

### Next Steps
- [ ] Fix critical findings
- [ ] Re-run `/security quick` to verify
- [ ] Schedule medium/low fixes

Read the full file on GitHub · 134 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.

2mo ago First seen · 134 lines · 48 tokens per session scan A a86e82f811fe

Subscribe to this mod's changes

security is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 781 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-31.

Security

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

systematic-debugging

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

obra/superpowers · 21 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

bilge-development-kit: Skill for Claude Code