spec-driven-claude-code: Skill for Claude Code

.claude/skills/security-review/SKILL.md

security-review is a skill for Claude Code from dinhnguyenngoc/spec-driven-claude-code. It costs 14 tokens per session (1,590 once invoked), scanned A, original, MIT.

A process for auditing a codebase for security weaknesses and producing a prioritized report. It checks issues such as exposed secrets, unsafe database queries, insecure data handling, and missing access controls.

In plain words
What is it for?
Use it to scan source code for hardcoded credentials, SQL injection risks, unsafe deserialization, and unprotected endpoints.
Why use it?
It helps identify security problems that could expose data, allow unauthorized actions, or make the application easier to attack.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is dinhnguyenngoc/spec-driven-claude-code's own configuration. It tells Claude Code how to work on spec-driven-claude-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spec-driven-claude-code configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dinhnguyenngoc/spec-driven-claude-code. 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/dinhnguyenngoc/spec-driven-claude-code/main/.claude/skills/security-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-code

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/dinhnguyenngoc/spec-driven-claude-code/security-review/github.svg)](https://agentmods.dev/skills/dinhnguyenngoc/spec-driven-claude-code/security-review)
Your own site
<a href="https://agentmods.dev/skills/dinhnguyenngoc/spec-driven-claude-code/security-review"><img src="https://agentmods.dev/badge/skills/dinhnguyenngoc/spec-driven-claude-code/security-review/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-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/dinhnguyenngoc/spec-driven-claude-code/security-review"><img src="https://agentmods.dev/badge/skills/dinhnguyenngoc/spec-driven-claude-code/security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,590 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Tool Misuse · line 67
    Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.
    Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
How audits are shown
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.00014 $0.01590
Opus 5 $0.00007 $0.00795
Sonnet 5 $0.00003 $0.00318
Haiku 4.5 $0.00001 $0.00159

Measured 8d ago against content hash 2dba9f1cb970, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

security-review 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 8d 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-review/SKILL.md · 202 lines

How it starts

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

Security Review Skill

Purpose

Systematically scan the codebase for security vulnerabilities and produce a prioritized report.

Boundary vs /scan: inside the /scan pipeline, do NOT run these tools manually — use the automation script .claude/scripts/scan-all.sh (per commands/scan.md Phase 0). This skill is the manual / ad-hoc variant for quick audits outside the pipeline.

Checklist

🔴 Critical (Check First)

  • Hardcoded secrets, API keys, passwords in source files
    grep -rn --include="*.cs" --include="*.json" \
      -E "(password|secret|apikey|api_key|connectionstring)\s*[:=]\s*['\"][^'\"]{8,}" src/
    
  • appsettings.json with real secrets committed
    git log --all --full-history -- "**/appsettings*.json"
    grep -rn "Password=" src/
    
  • SQL injection via string concatenation (Dapper raw queries)
    grep -rn --include="*.cs" "ExecuteAsync\|QueryAsync" src/ | grep -v "@"
    grep -rn --include="*.cs" '\$".*SELECT\|INSERT\|UPDATE\|DELETE' src/
    
  • Insecure deserialization
    grep -rn --include="*.cs" "JsonSerializer.Deserialize\|BinaryFormatter" src/
    

🟡 High Priority

  • Missing [Authorize] on protected endpoints
    grep -rn --include="*.cs" "\[HttpGet\]\|\[HttpPost\]\|\[HttpPut\]\|\[HttpDelete\]" src/ | \
      grep -v "\[Authorize\]"
    
  • Missing authorization checks (privilege escalation)
  • Passwords stored without hashing
    grep -rn --include="*.cs" "Password\s*=" src/ | grep -v "PasswordHash\|HashPassword"
    
  • JWT secrets too short or hardcoded
    grep -rn --include="*.cs" --include="*.json" "Jwt.*Secret" src/
    
  • No rate limiting on auth endpoints
    grep -rn --include="*.cs" "\[HttpPost\].*login\|signin\|register" src/
    
  • Missing FluentValidation on request DTOs
    # Check if validators exist for Request classes
    find src/ -name "*Request.cs" -exec basename {} \; | \
      while read f; do grep -l "${f%.*}Validator" src/ || echo "Missing: $f"; done
    

Read the full file on GitHub · 202 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. 8d ago First seen · 202 lines · 14 tokens per session scan A 2dba9f1cb970

Subscribe to this mod's changes

security-review is a skill published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (20 stars, last pushed 10d ago), licensed MIT. It adds 14 tokens to every session and 1,590 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-30.

Related

Other skills, from other repositories

specx-component-architecture

Design or review specx core scope boundaries in Python services. Use when deciding where code belongs across packaged scoped foundation bases, optional local foundation extensions, core/, capabilities, delivery, infrastructure, shared/, and ioc; when adding guardrails or splitting use cases, services, DTOs, schemas…

maksimzayats/specx · 74 tokens

specx-tests

Add or refine tests for specx Python services. Use when creating unit tests for use cases/services, integration tests for FastAPI controllers or infrastructure adapters, e2e smoke tests, architecture import guardrails, DI override tests, pytest fixtures, or coverage and boundary checks.

maksimzayats/specx · 58 tokens

specx-project-structure

Create or reshape a Python FastAPI service repo into the specx clean core/delivery architecture using packaged scoped foundation bases. Use when starting an API backend, adding the first src package, or establishing AGENTS.md, core/, optional local foundation/, delivery/, infrastructure, ioc/, migrations, and tests.

maksimzayats/specx · 75 tokens

specx-add-core-use-case

Add or refactor a specx core scope use case. Use when implementing an externally meaningful application action under a core scope usecases package, adding same-file command/query inputs, result DTOs, coordinating services, opening a unit-of-work transaction, or moving behavior out of delivery or infrastructure into…

maksimzayats/specx · 70 tokens

specx-add-infrastructure-adapter

Add technical infrastructure adapters for specx core scopes. Use when implementing SQLAlchemy repositories and Alembic-backed persistence, Redis stores, HTTP/network clients, file or queue adapters, unit-of-work implementations, gateway implementations for external APIs or SDKs such as OpenAI, or explicit diwire…

maksimzayats/specx · 76 tokens

specx-diwire-composition

Wire dependency injection for a specx Python service with diwire. Use when adding ioc/container.py, explicit dependency registrations for capabilities, repositories, gateways, UoW managers, clients, settings, or factories, Injected[...] constructor fields, FastAPI app factory/lifecycle composition, test overrides, or…

maksimzayats/specx · 83 tokens