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/anthropics/knowledge-work-plugins/guideline-generationnpx skills add anthropics/knowledge-work-plugins --skill guideline-generationgit clone --depth 1 https://github.com/anthropics/knowledge-work-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/anthropics/knowledge-work-plugins/guideline-generation)<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/guideline-generation"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/guideline-generation.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.00117 | $0.01498 |
| Opus 5 | $0.00059 | $0.00749 |
| Sonnet 5 | $0.00023 | $0.00300 |
| Haiku 4.5 | $0.00012 | $0.00150 |
Grade A, and why
guideline-generation 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 yesterday.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- guideline-generation — 100% identical, 0 lines differ
- guideline-generation — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guideline Generation
Generate comprehensive, LLM-ready brand voice guidelines from any combination of sources — brand documents, sales call transcripts, discovery reports, or direct user input. Transform raw materials into structured, enforceable guidelines with confidence scoring and open questions.
Inputs
Accept any combination of:
- Discovery report from the discover-brand skill (structured, pre-triaged)
- Brand documents uploaded or from connected platforms (PDF, PPTX, DOCX, MD, TXT)
- Conversation transcripts from Gong, Granola, manual uploads, or Notion meeting notes
- Direct user input about their brand voice and values
When a discovery report is provided, use it as the primary input — sources are already triaged and ranked. Supplement with additional analysis as needed.
Generation Workflow
1. Identify and Classify Sources
Determine what the user has provided. If no sources are available:
- Check if a discovery report exists from a previous
/brand-voice:discover-brandrun - Check
.claude/brand-voice.local.mdfor known brand material locations - Suggest running discovery first:
/brand-voice:discover-brand
2. Process Sources
For documents: Delegate to the document-analysis agent for heavy parsing. Extract voice attributes, messaging themes, terminology, tone guidance, and examples.
For transcripts: Delegate to the conversation-analysis agent for pattern recognition. Extract implicit voice attributes, successful language patterns, tone by context, and anti-patterns.
For discovery reports: Extract pre-triaged sources, conflicts, and gaps. Use the ranked sources directly.
3. Synthesize Into Guidelines
Merge all findings into a unified guideline document following the template in references/guideline-template.md. Key sections:
"We Are / We Are Not" Table — The core brand identity anchor:
| We Are | We Are Not |
|---|---|
| [Attribute — e.g., "Confident"] | [Counter — e.g., "Arrogant"] |
| [Attribute — e.g., "Approachable"] | [Counter — e.g., "Casual or sloppy"] |
What ships with it
2 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.
- yesterday First seen · 142 lines · 117 tokens per session scan A 9f5fd0e3d9ce
guideline-generation is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,849 stars, last pushed yesterday), licensed Apache-2.0. It adds 117 tokens to every session and 1,498 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-09-03.
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…