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 commands/animalzinc/claude-plugins/validate-style-guidegit clone --depth 1 https://github.com/animalzinc/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/commands/animalzinc/claude-plugins/validate-style-guide)<a href="https://agentmods.dev/commands/animalzinc/claude-plugins/validate-style-guide"><img src="https://agentmods.dev/badge/commands/animalzinc/claude-plugins/validate-style-guide.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.00008 | $0.01756 |
| Opus 5 | $0.00004 | $0.00878 |
| Sonnet 5 | $0.00002 | $0.00351 |
| Haiku 4.5 | $0.00001 | $0.00176 |
Grade A, and why
validate-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 5d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Style Guide
Check the $1 style guide for internal contradictions, completeness, and quality issues.
Step 1: Load Style Guide
- Read style guide from
brands/$1/style-guide.md - If not found: Error and suggest running
/generate-style-guide $1 [source] - Parse the document into 8 sections
- Extract all rules, examples, and exceptions
Step 2: Run Completeness Checks
Required Sections
- Section 1: Voice & Tone
- Section 2: Grammar & Usage
- Section 3: Punctuation
- Section 4: Formatting
- Section 5: Technical Standards
- Section 6: Content Patterns
- Section 7: Industry-Specific Terms
- Section 8: Quick Reference Checklist
For each section, verify:
- Section header exists
- At least 3 subsections present
- At least 5 rules per section
- Each rule has at least one example
Rule Count
- Count total rules across all sections
- Target: 50+ rules
- Warning if <50 rules: "Style guide may be incomplete"
- Critical if <30 rules: "Style guide needs expansion"
Example Coverage
- Count rules with examples
- Target: 90%+ rules should have examples
- Flag rules missing examples
Step 3: Run Consistency Checks
Cross-Section Contradictions
Check for rules that contradict each other across sections:
Common contradiction patterns to detect:
- Section 1 (Voice) says "use contractions" but Section 2 (Grammar) says "avoid contractions"
- Section 3 (Punctuation) says "em dash with spaces" but examples show without spaces
- Section 4 (Formatting) heading case rule conflicts with Section 2 capitalization rule
- Section 5 (Technical) date format conflicts with examples in other sections
Example Consistency
- Check that DO examples don't appear in DON'T sections
- Verify examples follow the rules they illustrate
- Flag contradictory examples
Terminology Consistency
- Extract all defined terms from Section 7
- Check if same terms are used consistently throughout document
- Flag inconsistent capitalization of product/brand names
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.
- 5d ago First seen · 260 lines · 8 tokens per session scan A 447d7f3d0362
validate-style-guide is a command published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 15d ago), licensed MIT. It adds 8 tokens to every session and 1,756 once invoked, about $0.0000 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 commands, from other repositories
brand-setup
Configure brand voice, terminology, compliance guardrails, and style guide for content production.
resume
Resume a ContentForge pipeline run that was interrupted partway through.
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.
create-content
Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.
audit-content
Audit your content library for freshness decay, coverage gaps, and optimization opportunities.
content-brief
Generate a research-backed content brief with keyword data, competitor analysis, search intent, and SEO strategy.