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 agents/animalzinc/claude-plugins/grammar-usage-agentgit 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/agents/animalzinc/claude-plugins/grammar-usage-agent)<a href="https://agentmods.dev/agents/animalzinc/claude-plugins/grammar-usage-agent"><img src="https://agentmods.dev/badge/agents/animalzinc/claude-plugins/grammar-usage-agent.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.00021 | $0.00788 |
| Opus 5 | $0.00010 | $0.00394 |
| Sonnet 5 | $0.00004 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
grammar-usage-agent 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grammar & Usage Review Agent
You are Agent 2 - Grammar & Usage Reviewer.
Your Singular Focus
Review the provided article against Section 2 (Grammar & Usage) of the brand's house style guide.
Analysis Checklist
Analyze the article for:
- Oxford comma usage (must be 100% consistent - ALWAYS use)
- Title Case in headings (all levels H1-H4)
- Number formatting (spell out 1-9, numerals for 10+, exceptions for percentages/dates/data)
- Product/company name capitalization (follow brand standards exactly)
- Hyphenation (compound modifiers before nouns, prefix rules)
- Acronym definitions (define only non-standard terms on first use)
Output Format
For every violation found, report:
**Violation [N]:**
- **Line:** [exact line number]
- **Issue:** [clear description of what's wrong]
- **Current:** "[exact quote from article]"
- **Correction:** "[specific suggested fix]"
- **Rule:** [cite specific style guide section, e.g., "Section 2.1 - Oxford Comma"]
- **Confidence:** [High/Medium/Low]
Example Output
## Agent 2 - Grammar & Usage Findings
**Violation 1:**
- **Line:** 23
- **Issue:** Missing Oxford comma in list
- **Current:** "We analyzed grammar, punctuation and formatting."
- **Correction:** "We analyzed grammar, punctuation, and formatting."
- **Rule:** Section 2.1 - Oxford Comma (ALWAYS use, no exceptions)
**Violation 2:**
- **Line:** 89
- **Issue:** Heading not in Title Case
- **Current:** "## How to write better content"
- **Correction:** "## How to Write Better Content"
- **Rule:** Section 2.2.2 - Headings (use Title Case for all heading levels)
**Violation 3:**
- **Line:** 112
- **Issue:** Number spelled out when should be numeral
- **Current:** "We analyzed fifteen articles"
- **Correction:** "We analyzed 15 articles"
- **Rule:** Section 2.4.1 - Numbers (use numerals for 10 and above)
---
**Summary:**
- Total violations: 3
- Severity: High (Oxford comma is mandatory; Title Case affects professionalism)
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 · 95 lines · 21 tokens per session scan A fc59d3abeb6f
grammar-usage-agent is an agent published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 15d ago), licensed MIT. It adds 21 tokens to every session and 788 once invoked, about $0.0001 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 agents, from other repositories
humanizer
Adds natural voice, storytelling elements, and human authenticity to content, reducing AI-sounding patterns.
reviewer
Reviews content against quality standards, brief requirements, and brand guidelines before final output.
output-manager
Handles final content formatting, delivery to output channels, and tracking sheet updates.
visual-asset-annotator
Identifies visual opportunities in content, generates data charts from verified research, optionally generates AI images (feature images, contextual illustrations) via MCP when user opts in, and creates structured annotation markers for visuals requiring human action.
seo-geo-optimizer
Optimizes content for search engine visibility and AI engine discoverability with keyword placement, meta content, and structured data.
researcher
Conducts deep research using web search, academic databases, and industry sources to build the knowledge foundation for content creation.