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.
npx skills add muyen/vibe-to-prod --skill security-scangit clone --depth 1 https://github.com/muyen/vibe-to-prodWrote 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.
[](https://agentmods.dev/skills/muyen/vibe-to-prod/security-scan)<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.
<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>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.00025 | $0.00598 |
| Opus 5.5 | $0.00010 | $0.00239 |
| Sonnet 5.5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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.
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
- Injection - Parameterized queries?
- Broken Auth - Session management secure?
- Sensitive Data - Encrypted at rest/transit?
- XXE - XML parsing disabled/secured?
- Broken Access Control - Authorization checked?
- Misconfiguration - Default configs changed?
- XSS - Output encoded?
- Deserialization - Untrusted data validated?
- Components - Dependencies up to date?
- 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/
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.
- 12d ago First seen · 106 lines · 25 tokens per session scan A 738091ca80e9
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.
Other skills, from other repositories
create-stories
Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics.
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
quick-design
Lightweight spec for small changes — tuning adjustments, minor mechanics. Embeds directly into stories; skips full GDD.
bug-report
Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.