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 skills add odere-pro/claude-oop-excellence --skill glossarygit clone --depth 1 https://github.com/odere-pro/claude-oop-excellenceWrote 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/skills/odere-pro/claude-oop-excellence/glossary)<a href="https://agentmods.dev/skills/odere-pro/claude-oop-excellence/glossary"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-oop-excellence/glossary/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/odere-pro/claude-oop-excellence/glossary"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-oop-excellence/glossary.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00092 | $0.01736 |
| Opus 5 | $0.00046 | $0.00868 |
| Sonnet 5 | $0.00018 | $0.00347 |
| Haiku 4.5 | $0.00009 | $0.00174 |
Grade A, and why
glossary 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 9d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Glossary
The canonical vocabulary for claude-oop-excellence. The sibling file glossary.json (in this same
skill directory) is the single source of truth for every entity the plugin recognizes — code
smells, antipatterns, vulnerabilities, supply-chain risks, and design patterns — plus the shared
vocabulary every other skill and scanner reads at runtime. When you need the authoritative record for
an entity, read glossary.json and return what it says verbatim. Do not invent fields or values.
Structure
glossary.json has two top-level keys.
vocabulary
Shared, enumerable terms used across the plugin:
categories—code-smell,antipattern,vulnerability,supply-chain-risk,design-pattern.families— issue families (oop,code,architecture,testing,concurrency,database,security,dependency) and pattern families (creational,structural,behavioral,architectural,enterprise,functional,ddd).severity_weights— numeric weight per severity (critical10,high5,medium2,low1).score_bands—clean,low,moderate,high,criticalthresholds for an aggregate score.scopes—full,changed,component.confidence— the0-100range scanners report.principles— the design principles entities reference (e.g.srp,ocp,lsp,isp,dip,encapsulation,high-cohesion,low-coupling,law-of-demeter,dry,kiss,yagni,composition-over-inheritance,tell-dont-ask).tracks— the two top-level audit tracks:risk(find issues) andpattern(work with design patterns).aspects— the work an audit can do within a track:risk-scan(detect issues),pattern-scan(detect design patterns already present),pattern-fit(suggest the most-suitable patterns).
entities
An array of entity records. Each record has:
id— stable kebab-case identifier (e.g.god-class). Use this to select an entity.name— human-readable name (e.g.God Class).category— one of thevocabulary.categories.family— one of thevocabulary.families.principles— for issues, the principles the entity violates; for design patterns, the principles it upholds.signs— language-neutral descriptions of what to look for. Plain English, never regex.default_severity—critical/high/medium/low(issues only).applies_when— the precondition for the entity to be in scope (e.g. "any class/struct/interface declarations present").corrective_patterns— (issues only) ids of design patterns that fix this issue.resolves— (design patterns only) ids of the issues this pattern fixes.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 115 lines · 92 tokens per session scan A 345ed17a20d0
glossary is a skill published in the GitHub repository odere-pro/claude-oop-excellence (1 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,736 once invoked, about $0.0005 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-31.
Other skills, from other repositories
code-review
Review code against enterprise standards — auto-detects stack (.NET, NestJS, React, RN, Flutter).
pr-review
Review current branch changes — reads git diff, runs stack-appropriate review, outputs structured feedback.
architecture-review
Review layer separation, design patterns, DI, and module boundaries.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…