bazinga: Skill for Claude Code

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

security-scan is a skill for Claude Code from mehdic/bazinga. It costs 68 tokens per session (1,181 once invoked), scanned A, original, MIT.

A code-security scanning skill that checks software for common vulnerabilities such as SQL injection, cross-site scripting, exposed secrets, and unsafe dependencies.

In plain words
What is it for?
Use it during code reviews, before approving changes or production releases, when security-sensitive code changes, or when checking dependencies and third-party code.
Why use it?
It gives reviewers a repeatable way to detect security risks before code is approved or deployed. SQL injection and cross-site scripting are attacks that can manipulate databases or inject harmful browser content.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

This is mehdic/bazinga's own configuration. It tells Claude Code how to work on bazinga 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 bazinga configures →

Reuse

Borrowing it

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

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/mehdic/bazinga/security-scan/github.svg)](https://agentmods.dev/skills/mehdic/bazinga/security-scan)
Your own site
<a href="https://agentmods.dev/skills/mehdic/bazinga/security-scan"><img src="https://agentmods.dev/badge/skills/mehdic/bazinga/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/mehdic/bazinga/security-scan"><img src="https://agentmods.dev/badge/skills/mehdic/bazinga/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,181 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.00068 $0.01181
Opus 5.5 $0.00027 $0.00472
Sonnet 5.5 $0.00014 $0.00236
Haiku 4.5 $0.00007 $0.00118

Measured 2mo ago against content hash b840c9409eec, 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 2mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/scan.ps1, scripts/scan.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-scan/SKILL.md · 176 lines

How it starts

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

Security Scanning Skill

You are the security-scan skill. When invoked, you run appropriate security scanners based on project language and provide structured security reports.

When to Invoke This Skill

Invoke this skill when:

  • Tech Lead is reviewing code changes
  • Before approving pull requests
  • Security-sensitive code modified (auth, database, API endpoints)
  • Before deployment to production
  • Reviewing dependencies or third-party code

Do NOT invoke when:

  • Documentation-only changes
  • Test file changes only
  • Non-code changes (README, config, .gitignore)
  • Work-in-progress drafts not ready for review

Your Task

When invoked:

  1. Execute the security scan script
  2. Read the generated security report
  3. Return a summary to the calling agent

Step 1: Execute Security Scan Script

Use the Bash tool to run the pre-built security scanning script.

On Unix/macOS:

bash .claude/skills/security-scan/scripts/scan.sh

On Windows (PowerShell):

pwsh .claude/skills/security-scan/scripts/scan.ps1

Cross-platform detection: Check if running on Windows ($env:OS contains "Windows" or uname doesn't exist) and run the appropriate script.

The script automatically determines scan mode:

  • Basic mode (default): Fast scan, high/medium severity only (5-10 seconds)
  • Advanced mode: Comprehensive scan, all severities (30-60 seconds)

Mode selection is controlled by SECURITY_SCAN_MODE environment variable (set by Tech Lead based on revision count).

The script will:

  • Detect project language (Python, JavaScript, Go, Ruby, Java)
  • Run appropriate security scanner (bandit, npm audit, gosec, brakeman, spotbugs)
  • Parse results and categorize by severity
  • Generate bazinga/artifacts/{SESSION_ID}/skills/security_scan.json

Step 2: Read Generated Report

Use the Read tool to read:

bazinga/artifacts/{SESSION_ID}/skills/security_scan.json

Extract key information:

  • scan_mode - Basic or advanced
  • status - success/partial/error
  • critical_issues, high_issues, medium_issues - Issue counts
  • issues - Array of security findings with file/line/recommendation

Read the full file on GitHub · 176 lines

Files

What ships with it

2 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. 2mo ago First seen · 176 lines · 68 tokens per session scan A b840c9409eec

Subscribe to this mod's changes

security-scan is a skill published in the GitHub repository mehdic/bazinga (22 stars, last pushed 9mo ago), licensed MIT. It adds 68 tokens to every session and 1,181 once invoked, about $0.0003 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

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