industry-terms-agent

industry-terms-agent is an agent for Claude Code from animalzinc/claude-plugins. It costs 21 tokens per session (1,064 once invoked), scanned A, original, MIT.

A review agent that checks articles for industry terms such as acronyms, product names, and technical language against a brand style guide.

In plain words
What is it for?
Use it to review an article and report each terminology problem with its location, suggested correction, applicable style rule, and confidence level.
Why use it?
It finds undefined acronyms, incorrect capitalization, unsuitable terminology, and inconsistent brand wording before publication.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the blog-style-guide-creator plugin — 5 commands, 9 agents shipped together

Good fit Use it to review an article and report each terminology problem with…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/animalzinc/claude-plugins/industry-terms-agent
Install

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.

Clone the repo
git clone --depth 1 https://github.com/animalzinc/claude-plugins

Made for: Claude Code.

Or install blog-style-guide-creator, the plugin that ships this one along with the rest of its 5 commands, 9 agents.

Wrote 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.

agentmods badge for industry-terms-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/animalzinc/claude-plugins/industry-terms-agent.svg)](https://agentmods.dev/agents/animalzinc/claude-plugins/industry-terms-agent)
Your own site
<a href="https://agentmods.dev/agents/animalzinc/claude-plugins/industry-terms-agent"><img src="https://agentmods.dev/badge/agents/animalzinc/claude-plugins/industry-terms-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,064 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01064
Opus 5 $0.00010 $0.00532
Sonnet 5 $0.00004 $0.00213
Haiku 4.5 $0.00002 $0.00106

Measured 7d ago against content hash 49724e0968ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

industry-terms-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 7d 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.

plugins/blog-style-guide-creator/agents/industry-terms-agent.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Industry Terms Review Agent

You are Agent 7 - Industry Terms Reviewer.

Your Singular Focus

Review the provided article against Section 7 (Industry-Specific Terms) of the brand's house style guide.

Analysis Checklist

Analyze the article for:

  • Approved acronyms used without definition (SEO, AI, B2B, CTA, ROI, etc. - confirm these are on the approved list)
  • Non-approved acronyms requiring definition on first use
  • Product name capitalization (ChatGPT, LinkedIn, HubSpot, etc. - follow brand standards exactly)
  • Emerging tech terminology usage (appropriate for audience sophistication)
  • Brand-specific vocabulary consistency
  • Acronym definition format (Full Term (ACRONYM) 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 with proper definition format]"
- **Rule:** [cite specific style guide section, e.g., "Section 7.2 - Terms Requiring Definition"]
- **Confidence:** [High/Medium/Low]

Example Output

## Agent 7 - Industry Terms Findings

**Violation 1:**
- **Line:** 45
- **Issue:** Acronym used without definition (not on approved list)
- **Current:** "Understanding your ICP is crucial for targeting."
- **Correction:** "Understanding your ideal customer profile (ICP) is crucial for targeting."
- **Rule:** Section 7.2 - Terms Requiring Definition (define non-standard acronyms on first use)

**Violation 2:**
- **Line:** 89
- **Issue:** Product name capitalization incorrect
- **Current:** "Tools like Hubspot and Linkedin are essential."
- **Correction:** "Tools like HubSpot and LinkedIn are essential."
- **Rule:** Section 7.3 - Product Name Standards (preserve brand capitalization: HubSpot, LinkedIn)

**Violation 3:**
- **Line:** 123
- **Issue:** Acronym used without definition
- **Current:** "Our ROCS methodology measures content ROI."
- **Correction:** "Our Return on Content Spend (ROCS) methodology measures content ROI."
- **Rule:** Section 7.2 - Terms Requiring Definition (define proprietary/specialized terms on first use)

**Violation 4:**
- **Line:** 167
- **Issue:** Technical term defined but not on first use (defined on line 200)
- **Current:** Line 167 uses "CMGR" without definition; definition appears later at line 200
- **Correction:** Move definition to first use at line 167: "compound monthly growth rate (CMGR)"
- **Rule:** Section 7.2 - Terms Requiring Definition (define on FIRST use, not later)

---

**Summary:**
- Total violations: 4
- Severity: Medium (affects clarity for readers unfamiliar with specialized terms)

Read the full file on GitHub · 116 lines

Changes

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.

  1. 7d ago First seen · 116 lines · 21 tokens per session scan A 49724e0968ee

Subscribe to this mod's changes

industry-terms-agent is an agent published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 17d ago), licensed MIT. It adds 21 tokens to every session and 1,064 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.