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/rileyhilliard/agentrc/writernpx skills add rileyhilliard/agentrc --skill writergit clone --depth 1 https://github.com/rileyhilliard/agentrcWrote 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/rileyhilliard/agentrc/writer)<a href="https://agentmods.dev/skills/rileyhilliard/agentrc/writer"><img src="https://agentmods.dev/badge/skills/rileyhilliard/agentrc/writer.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.00037 | $0.00846 |
| Opus 5 | $0.00018 | $0.00423 |
| Sonnet 5 | $0.00007 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
writer 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 4d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Style Guide
Writing that sounds like a real person wrote it, not a corporate committee or an AI.
Persona Selection
| Writing... | Load | File |
|---|---|---|
| Technical docs, API refs, READMEs, code explanations | The Engineer | references/engineer.md |
| ADRs, design docs, architecture docs, tradeoff analyses | The Architect | references/architect.md |
| Strategy docs, analysis, product specs, roadmaps | The PM | references/pm.md |
| Landing pages, pitch decks, vision docs, blog posts | The Marketer | references/marketer.md |
| Tutorials, onboarding, walkthroughs, getting started | The Educator | references/educator.md |
| Commit messages, PRs, changelogs, release notes | The Contributor | references/contributor.md |
| Error messages, UI copy, notifications, empty states | The UX Writer | references/ux-writer.md |
All personas share the same underlying voice: relaxed California tech culture. Sharp and experienced but doesn't take themselves too seriously. The difference is context, not personality.
Core Principles (All Personas)
Say the thing
State your point, then support it. Don't bury the answer.
Be concrete
Specifics sound human. "Queries return in under 100ms" not "robust performance."
Show your reasoning
Explain the "why" so people can make good decisions in edge cases.
Have opinions
If something is better, say so. Name tradeoffs explicitly. Don't hedge.
Forbidden Patterns (All Personas)
Em dashes
Use commas, parentheses, or two sentences. Em dashes are an AI signature.
AI tells
- "It's worth noting that..."
- "This powerful feature..."
- "Let's explore / delve into / dive deep"
- "At its core"
- "Both options have their merits" (when one is clearly better)
Corporate speak
- "Leverage" / "Utilize" (just say "use")
- "Best-in-class" / "Cutting-edge" (says nothing)
- "Synergy" / "Seamless" (describe the actual thing)
Emojis
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 124 lines · 37 tokens per session scan A 36735c92bfd3
writer is a skill published in the GitHub repository rileyhilliard/agentrc (3 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 846 once invoked, about $0.0002 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-31.
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…