What is using-glossary?

A project glossary lookup rule that reads `docs/sdd/domain-glossary.md` when it exists and keeps its term definitions and code mappings in mind during a task.

It helps match user language to the relevant code and flag conflicts between the user's wording and the shared glossary.

It reduces inconsistent naming and prevents guessing when a domain term has a defined meaning in the project.

using-glossary — Skill for Claude Code by onur-aslan/sdd

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.

Any agent

npx skills add onur-aslan/sdd --skill using-glossary

Clone the repo

git clone --depth 1 https://github.com/onur-aslan/sdd

Made for: Claude Code.

Or install vibecoding, the plugin that ships this one along with the rest of its 7 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/onur-aslan/sdd/using-glossary/github.svg)](https://agentmods.dev/skills/onur-aslan/sdd/using-glossary)

Your own site

<a href="https://agentmods.dev/skills/onur-aslan/sdd/using-glossary"><img src="https://agentmods.dev/badge/skills/onur-aslan/sdd/using-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/onur-aslan/sdd/using-glossary"><img src="https://agentmods.dev/badge/skills/onur-aslan/sdd/using-glossary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 187 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.

Model	Per session	Once invoked
Fable 5.1	$0.00016	$0.00187
Opus 5.5	$0.00006	$0.00075
Sonnet 5.5	$0.00003	$0.00037
Haiku 4.5	$0.00002	$0.00019

Measured 2d ago against content hash 54fe34931ba4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

vibecoding/skills/using-glossary/SKILL.md · 11 lines

What it actually says

If docs/sdd/domain-glossary.md exists in the project, read it before starting work. Keep its term-to-code mappings in mind for the rest of the task: use the same names the glossary uses, recognize a domain term when the user mentions it, and point to the matching code instead of guessing. If the file doesn't exist, proceed normally — no need to mention it unless the user brings up domain terminology.

If the user describes a term in a way that conflicts with its glossary definition, flag the mismatch before proceeding — quote the glossary's definition, point out the difference, and ask which one should hold. Don't silently go with either version.

If a term comes up that isn't in the glossary, just do the work — don't suggest adding it unless asked.

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.

2d ago First seen · 11 lines · 16 tokens per session scan A 54fe34931ba4

Subscribe to this mod's changes

using-glossary is a skill published in the GitHub repository onur-aslan/sdd (10 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 187 once invoked, about $0.0001 per session on Opus 5.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-11-12.

Writing and docs ai-agents claude sdd skills software-engineering spec-driven-development

using-glossary next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
using-glossaryonur-aslan/sdd	Skill	10	yesterday	MIT	A	16	Claude Code
subagent-driven-developmentrpamis/comet	Skill	3.3k	yesterday	MIT	A	17	Claude Code, Codex
cometrpamis/comet	Skill	3.3k	yesterday	MIT	A	44	Claude Code, Codex
comet-verifyrpamis/comet	Skill	3.3k	yesterday	MIT	A	32	Claude Code, Codex
comet-hotfixrpamis/comet	Skill	3.3k	yesterday	MIT	A	40	Claude Code, Codex
comet-tweakrpamis/comet	Skill	3.3k	yesterday	MIT	A	48	Claude Code, Codex
comet-reviewrpamis/comet	Skill	3.3k	yesterday	MIT	A	30	Claude Code, Codex