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 skills/ackeskin/contexture/glossarynpx skills add AcKeskin/contexture --skill glossarygit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/ackeskin/contexture/glossary)<a href="https://agentmods.dev/skills/ackeskin/contexture/glossary"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/glossary.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.1 | $0.00077 | $0.02624 |
| Opus 5 | $0.00039 | $0.01312 |
| Sonnet 5 | $0.00015 | $0.00525 |
| Haiku 4.5 | $0.00008 | $0.00262 |
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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glossary
The domain-vocabulary organ. Captures what a project's words mean — the Ubiquitous Language (DDD) — as a durable project-tier artefact: each load-bearing domain term with a one-line definition, the code symbol(s) that embody it, and a note where terms collide.
The third leg of the "observe-the-codebase-and-write-it-down" set: structure (codemap) + style (extract-conventions) + meaning (this). Codemap says what the modules are; conventions say how the code is styled; the glossary says what the domain nouns and verbs mean. Built to extract-conventions' shape — same author→prime→audit→project loop, same propose-confirm gate, same project-tier write, same hybrid mechanical-surfacing + confidence-flagged model-drafting.
Gates on the rule-prime hook for payoff: without the hook priming the glossary, it is an inert surface. Feeds naming-and-comments as the canonical-term reference its vocabulary-drift finding cites.
When to run
- User types
/glossary [scope](no arg → prompt for scope). - Natural language: "write down the project's domain terms", "define our vocabulary", "what does
Reconciler/Settlementmean — capture it", "build a glossary for this codebase". - Do not auto-fire. Mode A, user-invoked only. Defining a project's words is a deliberate act, never a session side effect. No hook, no session-start trigger.
Inputs
-
Scope — a directory (
src/billing/), a module, or the whole project (default). With no arg, prompt:What scope should I extract the vocabulary from? A directory, a module, or the whole project?
-
Working directory —
$CLAUDE_PROJECT_DIRorcwd. Anchors the write target (<project>/.claude/rules/glossary.md) and the rule-overlay resolution. -
Per-group accept/edit/reject decisions — collected at the confirm gate (§4). Never auto-write.
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.
- 2d ago First seen · 141 lines · 77 tokens per session scan A 144d3febb41b
glossary is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 2,624 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
ios-development
Comprehensive guide for building native Apple platform applications.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.
battle-card-builder
Competitive battle card creation for sales teams combining competitive intelligence, sales enablement, and document formatting. Use when building battle cards, competitive analysis decks, or win/loss analysis materials.