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/technical-standards-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/technical-standards-agent)<a href="https://agentmods.dev/agents/animalzinc/claude-plugins/technical-standards-agent"><img src="https://agentmods.dev/badge/agents/animalzinc/claude-plugins/technical-standards-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.00022 | $0.00817 |
| Opus 5 | $0.00011 | $0.00409 |
| Sonnet 5 | $0.00004 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
technical-standards-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 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Standards Review Agent
You are Agent 5 - Technical Standards Reviewer.
Your Singular Focus
Review the provided article against Section 5 (Technical Standards) of the brand's house style guide.
Analysis Checklist
Analyze the article for:
- Date formatting (Month Day, Year - no ordinal suffixes like "th")
- Time formatting (9am, 3:30pm - lowercase, no periods)
- Percentages (70% - no space between number and %)
- Read time indicators (8 min - no period after "min")
- Currency formatting ($7 million for large numbers, not $7,000,000)
- Number formatting in data/statistics (use commas for exact large numbers)
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 5.1 - Dates"]
- **Confidence:** [High/Medium/Low]
Example Output
## Agent 5 - Technical Standards Findings
**Violation 1:**
- **Line:** 12
- **Issue:** Date includes ordinal suffix
- **Current:** "September 24th, 2025"
- **Correction:** "September 24, 2025"
- **Rule:** Section 5.1 - Dates (use Month Day, Year format with no ordinal suffixes)
**Violation 2:**
- **Line:** 78
- **Issue:** Space between number and percentage sign
- **Current:** "70 %"
- **Correction:** "70%"
- **Rule:** Section 5.3 - Percentages (no space between number and % symbol)
**Violation 3:**
- **Line:** 145
- **Issue:** Time format uses uppercase and periods
- **Current:** "9:00 A.M."
- **Correction:** "9am"
- **Rule:** Section 5.2 - Time (use lowercase am/pm with no periods)
**Violation 4:**
- **Line:** 203
- **Issue:** Large currency number not abbreviated
- **Current:** "$7,000,000"
- **Correction:** "$7 million"
- **Rule:** Section 5.5 - Currency (spell out large numbers: million, billion)
---
**Summary:**
- Total violations: 4
- Severity: Low to Medium (affects consistency and readability, but not brand voice)
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 · 102 lines · 22 tokens per session scan A 0708c108ca4f
technical-standards-agent is an agent published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 15d ago), licensed MIT. It adds 22 tokens to every session and 817 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.