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 Filip-Podstavec/claude-leverage --skill glossary-initgit clone --depth 1 https://github.com/Filip-Podstavec/claude-leverageWrote 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/filip-podstavec/claude-leverage/glossary-init)<a href="https://agentmods.dev/skills/filip-podstavec/claude-leverage/glossary-init"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/glossary-init/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/filip-podstavec/claude-leverage/glossary-init"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/glossary-init.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.00119 | $0.02614 |
| Opus 5.5 | $0.00048 | $0.01046 |
| Sonnet 5.5 | $0.00024 | $0.00523 |
| Haiku 4.5 | $0.00012 | $0.00261 |
Grade A, and why
glossary-init 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 1mo 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/glossary-init
What it does
Bootstraps (or extends) GLOSSARY.md at the repo root — a human-curated
dictionary of domain terms specific to this repo. One entry per term:
1–2 sentence definition, optional aliases, optional code-path pointers.
The point: the next agent opening this repo greps GLOSSARY.md once
and stops hallucinating that "Lead" means a sales prospect when here
it means a journalist's article lead. Reading source to recover
domain meaning per session is O(N) tokens per term; a one-line glossary
entry is O(1).
This skill surfaces candidate terms (by frequency of identifier appearance in tracked code). It never invents definitions — the user types them, the skill structures the file. See ADR 0005 for the rationale.
When to invoke
- First setup of an AI-first repo (after
/init-repo). - When you notice an agent halucinating the meaning of a recurring
domain term ("I think
Leadis a sales prospect" — no, it's a journalist's article). - Periodically as the domain vocabulary grows — re-run to add new terms (existing entries are preserved).
Do NOT invoke for:
- Code-level documentation (those go in docstrings / type hints).
- Cross-project / cross-client patterns (those live in the user's PKB, not in this repo's glossary).
- "What does this function do?" — that's what the code shows.
Workflow
-
Resolve repo root.
git rev-parse --show-toplevel. If not in a git repo, STOP and report: "glossary needs a tracked repo;git initfirst or run/init-repo". -
Detect mode.
- If
GLOSSARY.mddoes not exist at root → bootstrap mode. - If
GLOSSARY.mdexists and$ARGUMENTSincludes--add <term>→ single-add mode (skip candidate ranking, jump to step 6 for that one term). - If
GLOSSARY.mdexists and no--add→ extend mode: surface candidates that aren't already in the existing file, propose additions.
- If
-
Detect primary language by file extension counts in tracked files (
git ls-files | head -2000):.py→ Python.ts/.tsx/.js/.jsx→ TypeScript / JavaScript.go→ Go.rs→ Rust- Mixed → use all detected.
- Override with
--lang.
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.
- 1mo ago First seen · 248 lines · 119 tokens per session scan A 0b9d18d81685
glossary-init is a skill published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 2mo ago), licensed MIT. It adds 119 tokens to every session and 2,614 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
handoff
Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work…
opik-evaluate
Build an LLM evaluation and run it against the app, returning an Opik experiment with scores and its link. Picks a test suite with judge assertions or a dataset with metrics, sources cases from traces or synthetic data, scores heuristics-first then one-failure-mode judges, runs client-side via the SDK or server-side…
opik
Reference for the Opik SDK — tracing, span types, framework integrations, threads, and the prompt library (Python, TypeScript, REST). Use for "what span types exist", "how do I flush", "trackopenai", "add OpikTracer", "version a prompt". To instrument a repo end to end, use the opik-instrument skill.
hyper-plan
Use when about to start a non-trivial implementation that needs decomposition before coding. Also when the user invokes /hyperclaude:hyper-plan. Produces an ordered, bite-sized plan in .hyperclaude/plans/ — the input for /hyperclaude:hyper-plan-review and /hyperclaude:hyper-implement.
flow-create
Build a correct draft marketing scenario (flow) from a plain-language request: read the flows reference, resolve the entities the design needs to real ids, create and fill the blocks, wire the outputs, verify every block by reading it back, and hand over a link. Use when asked to create, build, assemble or set up a…
git-workflow
Enforces the release-branch Git model: scaffold feature branches, open PRs with review checks, cut releases with tags, and view workflow reference.