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 agentmods add skills/mrhinkle/vibecoding-a-website/security-auditornpx skills add mrhinkle/VibeCoding-a-Website --skill security-auditorgit clone --depth 1 https://github.com/mrhinkle/VibeCoding-a-WebsiteWrote 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/mrhinkle/vibecoding-a-website/security-auditor)<a href="https://agentmods.dev/skills/mrhinkle/vibecoding-a-website/security-auditor"><img src="https://agentmods.dev/badge/skills/mrhinkle/vibecoding-a-website/security-auditor.svg" alt="Measured on agentmods" 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 | $0.00130 | $0.02559 |
| Opus 5 | $0.00065 | $0.01280 |
| Sonnet 5 | $0.00026 | $0.00512 |
| Haiku 4.5 | $0.00013 | $0.00256 |
Grade A, and why
security-auditor 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 3d 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor
Why This Matters
You're building a website with real API keys (Resend, Beehiiv, etc.), form submissions, and serverless functions—but you might not have a security background. That's okay. This audit checks what you can't see: exposed credentials, outdated packages with known vulnerabilities, missing security headers, and privacy compliance gaps.
Security isn't optional. A breached API key can cost thousands. XSS vulnerabilities let hackers steal data from your visitors. This skill finds and fixes these issues in plain language.
Audit Areas
1. Secrets Scanning (Critical)
What we check:
- All files for exposed API keys, tokens, passwords
- Git history for accidentally committed secrets
- .env file is in .gitignore
- Hardcoded credentials in JavaScript/functions
- Vercel environment variables properly scoped
Why it matters: One exposed Resend key gives someone your email sending ability. One leaked database URL lets them access your data.
How to fix:
- Never commit .env files
- Use Vercel Environment Variables (Settings → Environment Variables)
- Rotate any exposed credentials immediately
- Add this to .gitignore:
.env.local,.env,*.pem
2. Dependency Vulnerabilities
What we check:
- Run
npm auditfor known CVEs - Identify outdated packages with security patches
- Classify severity (Critical, High, Medium, Low)
Why it matters: Your dependencies might have known exploits. A vulnerable library is a backdoor waiting to be used.
How to fix:
npm audit fix # Auto-fix minor vulnerabilities
npm audit fix --force # Fix breaking changes (test after)
npm outdated # See what's outdated
3. Security Headers Audit
These headers tell browsers how to handle your site safely. Missing them = leaving doors unlocked.
Content-Security-Policy (CSP) Prevents inline scripts and restricts where resources load from.
// vercel.json
{
"headers": [
{
"source": "/(.*)",
"headers": [
{
"key": "Content-Security-Policy",
"value": "default-src 'self'; script-src 'self' 'unsafe-inline' cdn.vercel.com; style-src 'self' 'unsafe-inline'"
}
]
}
]
}
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.
- 3d ago First seen · 358 lines · 130 tokens per session scan A 23f44c029346
security-auditor is a skill published in the GitHub repository mrhinkle/VibeCoding-a-Website (11 stars, last pushed 4mo ago), licensed MIT. It adds 130 tokens to every session and 2,559 once invoked, about $0.0006 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…