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/code-auditornpx skills add mrhinkle/VibeCoding-a-Website --skill code-auditorgit clone --depth 1 https://github.com/mrhinkle/VibeCoding-a-WebsiteWhat 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.00114 | $0.03465 |
| Opus 5 | $0.00057 | $0.01733 |
| Sonnet 5 | $0.00023 | $0.00693 |
| Haiku 4.5 | $0.00011 | $0.00347 |
Grade A, and why
code-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 2d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Auditor
The code-auditor skill ensures that the JavaScript, HTML, and CSS running your website is correct, robust, and follows best practices. While the performance-optimizer focuses on speed and file size, the code-auditor focuses on correctness: Does your code run without errors? Do your API integrations actually work? Is there proper error handling in place? Are your dependencies secure?
This skill is your "web programmer" — the person who makes sure everything runs without breaking.
JavaScript Audit
Console Error Detection
Scans your browser console for JavaScript errors with zero-error tolerance in production. Checks:
- Uncaught errors and exceptions
- Unhandled promise rejections (async operations that fail silently)
- TypeError, ReferenceError, SyntaxError messages
- Deprecation warnings that could break in future browser updates
- Security warnings (mixed content, unsafe operations)
Why it matters: Users see broken functionality and get frustrated. Search engines penalize sites with errors.
API Call Failures
Tests all fetch() and XMLHttpRequest calls:
- Failed requests (4xx, 5xx responses)
- Network timeout issues
- Malformed request headers or bodies
- CORS errors when calling external APIs
- Missing or invalid API keys blocking requests
Why it matters: If your contact form can't submit to Resend, or your analytics don't load, visitors won't know — they'll just see a broken site.
Memory Leaks & Event Listeners
Identifies JavaScript that keeps eating memory:
- Event listeners never removed (onclick handlers that stack up)
- Old data stored in variables but never cleaned up
- DOM nodes kept in memory after being removed from the page
- Timer intervals/timeouts that never clear
Why it matters: Your site gets slower and slower the longer users stay on it. On mobile, it can crash.
Dead Code & Unused Variables
Finds code that's not being used:
- Functions defined but never called
- Variables assigned but never read
- Imports that don't get used
- Conditional branches that will never execute
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.
- 2d ago First seen · 439 lines · 114 tokens per session scan A ddadacd25691
code-auditor is a skill published in the GitHub repository mrhinkle/VibeCoding-a-Website (11 stars, last pushed 4mo ago), licensed MIT. It adds 114 tokens to every session and 3,465 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…