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/bdfinst/agentic-dev-team/naming-reviewgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWhat 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.00014 | $0.01610 |
| Opus 5 | $0.00007 | $0.00805 |
| Sonnet 5 | $0.00003 | $0.00322 |
| Haiku 4.5 | $0.00001 | $0.00161 |
Grade A, and why
naming-review 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 3d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming Review
Scope: always Verify-model: haiku Verify-effort: medium
Cites:
- design-smells
- adversarial-review-protocol
- agent-review-methodology
Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).
Status (derive from the highest-severity finding, do not let finding volume alone change the tier): fail when any finding is error (misleading name) or warning (unclear name, magic value, or inconsistent naming) — both harm readability; warn when the only findings are suggestion (style); pass when there are no findings.
Severity: error=misleading names, warning=unclear, suggestion=style
Confidence: high=mechanical (add is/has prefix, extract magic value to constant); medium=better name suggested but domain context may differ; none=requires human judgment (domain terminology choices)
Context needs: diff-only
Knowledge Files
Read the "Naming Offender Catalog" section of ${CLAUDE_PLUGIN_ROOT}/knowledge/design-smells.md#naming-offender-catalog before analysis. It contains: abbreviation anti-patterns with fix pairs, generic verb offenders, misleading name patterns, and type-encoded name examples — as well as the "What NOT to flag" list to avoid false positives.
Skip
Return {"status": "skip", "issues": [], "summary": "No code files with nameable symbols"} when:
- Target contains only binary files, images, or generated code
- No files with variable/function/class declarations
Protocol
Run the shared three-phase methodology in ${CLAUDE_PLUGIN_ROOT}/knowledge/agent-review-methodology.md (Whole-file load: the Enumerate/Classify/Group phases and their rationale, read in full) — enumerate first, classify second, group third.
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.
- 3d ago First seen · 134 lines · 14 tokens per session scan A 12a34ff0689f
naming-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (277 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 1,610 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.