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 tdimino/claude-code-minoan --skill glossarygit clone --depth 1 https://github.com/tdimino/claude-code-minoanWrote 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/tdimino/claude-code-minoan/glossary)<a href="https://agentmods.dev/skills/tdimino/claude-code-minoan/glossary"><img src="https://agentmods.dev/badge/skills/tdimino/claude-code-minoan/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/tdimino/claude-code-minoan/glossary"><img src="https://agentmods.dev/badge/skills/tdimino/claude-code-minoan/glossary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.00607 |
| Opus 5 | $0.00049 | $0.00303 |
| Sonnet 5 | $0.00020 | $0.00121 |
| Haiku 4.5 | $0.00010 | $0.00061 |
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 10d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Glossary — Domain Language Builder
Build or update a CONTEXT.md at the project root that captures the project's domain language. A shared vocabulary between user and agent reduces verbosity (agents stop using 20 words where 1 domain term suffices), enforces consistent naming in code, and prevents terminology drift across sessions.
Creating a new CONTEXT.md
If no CONTEXT.md exists at the project root, run an elicitation session to discover domain terms:
- Explore the codebase to identify domain-specific naming patterns—types, modules, key abstractions, recurring nouns in variable names and comments.
- Present findings to the user: "I found these domain concepts in the code: [list]. Which are worth defining? Are any named inconsistently?"
- For each confirmed term, resolve four fields: the canonical name, a one-sentence definition, aliases to avoid, and relationships to other terms. These four fields are the minimum needed for an agent to use the term correctly and consistently—fewer leads to ambiguity, more adds noise.
- Ask about ambiguities: "Is [term] the same as [similar term], or are they distinct?" Surface these early because unresolved synonyms are the primary source of naming inconsistency in agent-generated code.
- Write
CONTEXT.mdfollowing the format in references/context-format.md.
Updating an existing CONTEXT.md
If CONTEXT.md already exists, read it first. Then:
- Identify the new concept or ambiguity that triggered this invocation.
- Check whether it fits an existing term (update the definition) or is genuinely new (add it).
- If the new concept conflicts with an existing term, add it to "Flagged ambiguities" with a clear resolution.
- Preserve all existing content—append, don't rewrite. Rewriting destroys cross-session term provenance and risks silently dropping terms other sessions depend on.
Consuming CONTEXT.md during other work
When exploring or modifying code in a project that has a CONTEXT.md:
What ships with it
2 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.
- 10d ago First seen · 36 lines · 98 tokens per session scan A 52942b970ab7
glossary is a skill published in the GitHub repository tdimino/claude-code-minoan (41 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 607 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-30.
Other skills, from other repositories
manager
A session-to-GitHub tracker that creates, updates, and reads issues across repositories, including their labels, parent epics, and project-board placement.
weekly-retro
A structured weekly retrospective for a one-person business run with AI agents. It gathers evidence from code, project tools, and canonical business files, then records findings and outcomes.
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
corp-doctor
A guided maintenance and setup tool for a Personal Corp system, meaning a business workflow built from AI agents, department repositories, and shared rules. It checks what exists before making changes.
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…
idea
Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub Project view filtered by label:idea. NOT…