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/webmasternpx skills add mrhinkle/VibeCoding-a-Website --skill webmastergit 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.02599 |
| Opus 5 | $0.00057 | $0.01300 |
| Sonnet 5 | $0.00023 | $0.00520 |
| Haiku 4.5 | $0.00011 | $0.00260 |
Grade A, and why
webmaster 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Webmaster Skill
Think of the webmaster as your site's project manager. While other skills are specialists (the SEO expert, the designer, the security guard), the webmaster sees the whole picture, knows who needs to do what and when, and produces a unified health report that tells you if your site is truly ready.
What The Webmaster Does
The webmaster orchestrates the full lifecycle of your website:
Planning Phase → Interview and define site goals, brand identity, audience
Building Phase → Generate initial site structure, wire forms, create content
Testing Phase → Run QA tests, security audits, SEO checks, copy review, UX evaluation
Deployment Phase → Check links, optimize performance, deploy to production
Monitoring Phase → Track ongoing health, detect regressions, flag issues
Iteration Phase → Update content, fix bugs, improve based on audit feedback
You don't need to remember what to check or the order to check it—the webmaster knows the playbook.
Workflow Presets
Pick the workflow that matches your situation:
Pre-Launch Review
When: 48 hours before going live. You've built your site and want to make sure it's truly production-ready.
What runs:
- QA Tester (broken links, forms, functionality)
- Security Auditor (vulnerabilities, data exposure)
- SEO/AEO Auditor (search visibility, answer engine optimization)
- Copy Editor (grammar, tone, brand consistency)
- UX Reviewer (usability, accessibility, navigation)
- Link Checker (all internal/external links valid)
- Performance Optimizer (page speed, Core Web Vitals)
Output: A single Pre-Launch Report with:
- Overall readiness score (0–100)
- Critical blockers (fix before launch)
- High-priority issues (fix within 1 week)
- Nice-to-haves (optimize after launch)
- Time estimate to fix everything
Typical time: 30–45 minutes to complete all audits
Quick Update
When: You've made changes (updated copy, fixed a bug, added a page) and want confidence they work.
What runs:
- Site Updater (applies your changes)
- Link Checker (ensures nothing broke)
- Performance Optimizer (no speed regressions)
- Auto-deploys to staging, then production if all clear
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 · 334 lines · 114 tokens per session scan A 33c58d657947
webmaster 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 2,599 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.