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/copy-editornpx skills add mrhinkle/VibeCoding-a-Website --skill copy-editorgit 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/copy-editor)<a href="https://agentmods.dev/skills/mrhinkle/vibecoding-a-website/copy-editor"><img src="https://agentmods.dev/badge/skills/mrhinkle/vibecoding-a-website/copy-editor.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.00098 | $0.02701 |
| Opus 5 | $0.00049 | $0.01350 |
| Sonnet 5 | $0.00020 | $0.00540 |
| Haiku 4.5 | $0.00010 | $0.00270 |
Grade A, and why
copy-editor 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copy Editor Skill
What This Skill Does
Your content-auditor catches typos. Your copy-editor catches weak sales pitches. This skill applies proven copywriting frameworks to every page on your website, answering the one question that matters: Is this actually persuading anyone to do anything?
The difference: A grammar check finds "their/there/they're." A copy review finds "Your homepage headline took 12 words to say what Slack says in 3."
Core Copywriting Frameworks
AIDA (Attention, Interest, Desire, Action)
Best for: Landing pages, homepages, hero sections
- Attention: Does your headline stop scrolling? (Power words, specificity, emotional trigger)
- Interest: Does the subhead explain why they should care? (Benefit, not feature)
- Desire: Does the body copy make them want it? (Social proof, specificity, visualization)
- Action: Is the CTA obvious and compelling? (Clear value, low friction, one primary call)
Example: Instead of "Cloud Storage Solutions" → "Keep Your Files Safe Everywhere—No Lost Documents Ever Again"
PAS (Problem, Agitate, Solution)
Best for: Services pages, case studies, problem-aware audiences
- Problem: Name the specific pain point
- Agitate: Show why it costs them money/time/stress (make them feel it)
- Solution: Present your offering as the obvious answer
Example: Problem: "Your team can't find files." Agitate: "That costs you 2 hours weekly." Solution: "Here's the system that lets anyone find anything in 10 seconds."
BAB (Before, After, Bridge)
Best for: About pages, results-driven content, transformation stories
- Before: Where your audience was (struggling, frustrated, lost)
- After: Where they could be (confident, winning, solved)
- Bridge: How your product/service gets them there
Example: Before: "Scattered across five tools." After: "One dashboard, perfect clarity." Bridge: "That's why teams choose [Your Product]."
4 Ps (Promise, Picture, Proof, Push)
Best for: CTAs, conversion sections, high-stakes asks
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 · 287 lines · 98 tokens per session scan A 4d2c9339565a
copy-editor is a skill published in the GitHub repository mrhinkle/VibeCoding-a-Website (11 stars, last pushed 4mo ago), licensed MIT. It adds 98 tokens to every session and 2,701 once invoked, about $0.0005 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…