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 skills add Triumph-Tech/rock-claude-plugins --skill build-my-style-guidegit clone --depth 1 https://github.com/Triumph-Tech/rock-claude-pluginsWrote 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/triumph-tech/rock-claude-plugins/build-my-style-guide)<a href="https://agentmods.dev/skills/triumph-tech/rock-claude-plugins/build-my-style-guide"><img src="https://agentmods.dev/badge/skills/triumph-tech/rock-claude-plugins/build-my-style-guide/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/triumph-tech/rock-claude-plugins/build-my-style-guide"><img src="https://agentmods.dev/badge/skills/triumph-tech/rock-claude-plugins/build-my-style-guide.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00139 | $0.02494 |
| Opus 5 | $0.00069 | $0.01247 |
| Sonnet 5 | $0.00028 | $0.00499 |
| Haiku 4.5 | $0.00014 | $0.00249 |
Grade A, and why
build-my-style-guide 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 9d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build My Style Guide
This skill creates a personal writing style guide through a short writing interview. Rather than asking people to describe their style in the abstract, it asks them to write small pieces — exactly the kind of thing they send every day. Those samples reveal voice, rhythm, and mechanics more accurately than any multiple-choice question.
What this produces
A context/style-guide.md file in the person's Claude Workspace, containing:
- Specific, actionable voice rules derived from their actual writing
- Quick-reference templates for their most common writing situations
- An explicit avoid list
How to run the interview
Ask each question individually, one at a time. Wait for the person's response before moving to the next question. Do not batch questions together.
Keep your framing minimal between questions — a one-line transition is enough. This should feel like a quick writing exercise, not a form.
Before the first question, introduce the interview with this framing:
"This is a short writing interview designed to capture your unique voice and tone. The output is a personal style guide Claude can use to draft and polish communications that actually sound like you. I'll ask you 8 questions — each one is a short writing prompt, not a multiple-choice question. Just write naturally, the way you actually would. It takes about 10 minutes.
One important note: don't paste in AI-generated or heavily polished content — if it doesn't sound like your unedited self, the style guide won't either. Write your answers fresh in the prompt window, or paste in something you wrote yourself that you haven't run through an AI tool."
Then ask for their first name:
"Before we get started — what's your first name?"
Use their name to title the style guide file.
The Questions
Q1 — Client email opener
"Open an email to a client you have not been in touch with for a couple of weeks. Write the full opening: your greeting, a warm beat, and what you are reaching out about. Aim for 3 to 5 sentences."
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.
- 9d ago First seen · 219 lines · 139 tokens per session scan A bb1cd4507643
build-my-style-guide is a skill published in the GitHub repository Triumph-Tech/rock-claude-plugins (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 139 tokens to every session and 2,494 once invoked, about $0.0007 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…