security-check

security-check is a skill for Claude Code, Codex from ao92265/claude-code-playbook. It costs 86 tokens per session (756 once invoked), scanned A, original, MIT.

A quick security review of recent code changes, covering common web-application risks from the OWASP Top 10 list.

In plain words
What is it for?
Use it to scan changed files for hardcoded credentials, injection risks, unsafe browser output, path traversal, and insecure dependencies.
Why use it?
It helps find exposed secrets, unsafe input handling, cross-site scripting, and other security problems before code is released.

Skill for Claude CodeCodex

Part of the playbook plugin — 49 skills, 4 hooks shipped together

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.

agentmods
npx agentmods add skills/ao92265/claude-code-playbook/security-check
Any agent
npx skills add ao92265/claude-code-playbook --skill security-check
Clone the repo
git clone --depth 1 https://github.com/ao92265/claude-code-playbook

Made for: Claude Code, Codex.

Or install playbook, the plugin that ships this one along with the rest of its 49 skills, 4 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/security-check.svg)](https://agentmods.dev/skills/ao92265/claude-code-playbook/security-check)
Your own site
<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/security-check"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/security-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 756 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00086 $0.00756
Opus 5 $0.00043 $0.00378
Sonnet 5 $0.00017 $0.00151
Haiku 4.5 $0.00009 $0.00076

Measured 5d ago against content hash 78bcda913121, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

security-check 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 5d 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.

skills/security-check/SKILL.md · 74 lines

How it starts

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

Security Check

Quick security scan focused on recent changes. Checks for OWASP Top 10 patterns.

Steps

  1. Identify scope:

    • Get recently changed files: git diff --name-only HEAD~5 (or since last tag)
    • If no recent changes, scan staged files or ask the user for scope
  2. Scan for hardcoded secrets (CRITICAL):

    • API keys: patterns like AKIA, sk-, ghp_, xox[bpas]-
    • Passwords: password\s*=\s*["'], secret\s*=\s*["']
    • Private keys: -----BEGIN.*PRIVATE KEY-----
    • Connection strings with embedded credentials
    • JWT tokens: eyJ prefixed strings
    • Report file and line number for each finding
  3. Check for injection vulnerabilities (HIGH):

    • SQL injection: string concatenation in SQL queries, missing parameterized queries
    • Command injection: unsanitized input in exec(), spawn(), system(), eval()
    • Template injection: user input in template strings without escaping
    • Path traversal: user input in file paths without validation
  4. Check for XSS patterns (HIGH):

    • dangerouslySetInnerHTML with user-controlled content
    • innerHTML assignments with dynamic content
    • Unescaped output in templates (e.g., {!! !!} in Blade, | safe in Jinja)
  5. Check for authentication/authorization issues (HIGH):

    • Missing auth middleware on new routes
    • Overly permissive CORS (Access-Control-Allow-Origin: *)
    • Missing CSRF protection on state-changing endpoints
    • Hardcoded JWT secrets or weak signing algorithms
  6. Check dependencies (MEDIUM):

    • Run npm audit / pip audit / cargo audit as appropriate
    • Flag any critical or high severity vulnerabilities
    • Check for known vulnerable package versions
  7. Check for information disclosure (MEDIUM):

    • Stack traces exposed in error responses
    • Debug mode enabled in production configs
    • Verbose logging of sensitive data (passwords, tokens, PII)
  8. Report findings:

    • Group by severity: Critical, High, Medium, Low
    • Include file path, line number, and code snippet for each finding
    • Provide specific remediation advice for each issue
    • Summarize: total findings by severity, overall risk assessment

Read the full file on GitHub · 74 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. 5d ago First seen · 74 lines · 86 tokens per session scan A 78bcda913121

Subscribe to this mod's changes

security-check is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 19d ago), licensed MIT. It adds 86 tokens to every session and 756 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens