security-scan

security-scan is a skill for Claude Code from muyen/vibe-to-prod. It costs 25 tokens per session (598 once invoked), scanned A, original, MIT.

A security-scanning skill that checks changes involving authentication, APIs, user data, databases, files, payments, and other sensitive operations. Its checks cover access control, input validation, data protection, and API safety.

In plain words
What is it for?
Use it when adding or changing login checks, API endpoints, database queries, uploads, storage, payment features, or Firebase security rules.
Why use it?
It helps find missing permissions, unsafe inputs, exposed secrets or personal data, insecure file handling, and overly broad database access.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the vibe-to-prod-skills plugin — 8 skills shipped together

Good fit Use it when adding or changing login checks, API endpoints, database queries, uploads, storage, payment features, or Firebase security rules.

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

Made for: Claude Code.

Or install vibe-to-prod-skills, the plugin that ships this one along with the rest of its 8 skills.

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/muyen/vibe-to-prod/security-scan/github.svg)](https://agentmods.dev/skills/muyen/vibe-to-prod/security-scan)
Your own site
<a href="https://agentmods.dev/skills/muyen/vibe-to-prod/security-scan"><img src="https://agentmods.dev/badge/skills/muyen/vibe-to-prod/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/muyen/vibe-to-prod/security-scan"><img src="https://agentmods.dev/badge/skills/muyen/vibe-to-prod/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 598 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.00025 $0.00598
Opus 5.5 $0.00010 $0.00239
Sonnet 5.5 $0.00005 $0.00120
Haiku 4.5 $0.00003 $0.00060

Measured 12d ago against content hash 738091ca80e9, 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 12d 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-scan/SKILL.md · 106 lines

How it starts

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

Security Scan Skill

Automatically scans for security issues when security-sensitive code is modified.

When to Activate

This skill should activate when:

  • Changes touch authentication or authorization
  • New API endpoints are added
  • User input handling is modified
  • Database queries are added/modified
  • File uploads or storage operations
  • Payment or financial operations

Security Checklist

1. Authentication & Authorization

  • Auth middleware applied to protected routes
  • Firebase Auth tokens properly validated
  • User can only access their own data
  • Admin endpoints properly restricted

2. Input Validation

  • All user inputs validated
  • Request body size limits
  • File upload type/size restrictions
  • Path traversal prevention

3. Data Protection

  • No sensitive data in logs
  • No secrets in code
  • PII properly handled
  • Signed URLs used for private files

4. API Security

  • Rate limiting considered
  • CORS properly configured
  • Error messages don't leak info
  • Proper HTTP status codes

5. Firebase/Firestore Security

  • Security rules updated for new collections
  • Rules tested with Firebase emulator
  • No wildcard read/write rules
  • Proper field-level validation

OWASP Top 10 Quick Check

  1. Injection - Parameterized queries?
  2. Broken Auth - Session management secure?
  3. Sensitive Data - Encrypted at rest/transit?
  4. XXE - XML parsing disabled/secured?
  5. Broken Access Control - Authorization checked?
  6. Misconfiguration - Default configs changed?
  7. XSS - Output encoded?
  8. Deserialization - Untrusted data validated?
  9. Components - Dependencies up to date?
  10. Logging - Security events logged?

Platform-Specific Checks

Backend (Go)

# Run security scan
cd backend && make security-scan

# Check for vulnerabilities
cd backend && make vuln-check

Web (Next.js)

# Check npm vulnerabilities
cd web && npm audit

# Check for secrets
grep -r "api_key\|secret\|password" web/src/

Read the full file on GitHub · 106 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. 12d ago First seen · 106 lines · 25 tokens per session scan A 738091ca80e9

Subscribe to this mod's changes

security-scan is a skill published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 598 once invoked, about $0.0001 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-10-04.