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 commands/vishalj99/claude-docker/define-termsgit clone --depth 1 https://github.com/VishalJ99/claude-dockerWrote 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/commands/vishalj99/claude-docker/define-terms)<a href="https://agentmods.dev/commands/vishalj99/claude-docker/define-terms"><img src="https://agentmods.dev/badge/commands/vishalj99/claude-docker/define-terms.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 | $0.00010 | $0.01335 |
| Opus 5 | $0.00005 | $0.00668 |
| Sonnet 5 | $0.00002 | $0.00267 |
| Haiku 4.5 | $0.00001 | $0.00134 |
Grade A, and why
define-terms 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 4d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Define Terms
Terms to Define
$ARGUMENTS
Before Starting
- Check for inconsistencies in the provided terms — flag duplicates, overlapping concepts, or contradictory definitions
- Ask for clarification if any term is vague, ambiguous, or could have multiple interpretations
- Do not proceed until inconsistencies are resolved
Mode
If docs/dictionary.md and docs/dictionary/ already exist, update them by adding new entries. Do not recreate or overwrite existing entries unless explicitly asked.
Initialisation: Ensure project CLAUDE.md Has Vocabulary Protocol
Check if .claude/CLAUDE.md contains a "Shared Vocabulary Protocol" section.
If not present:
- Read `~/.claude/commands/claude-vocab-section.md
- Append its contents to the project-level
CLAUDE.md
This ensures agents know how to use the dictionary at runtime.
Objective
Generate entries in docs/dictionary.md index file that serves as the canonical source of truth for domain-specific terminology in this project. The index is loaded at session start; full entries are read on-demand.
The Problem This Solves
Terms like "committed state" or "editor" have project-specific meanings that differ from their general usage. Without explicit definitions, agents must guess—leading to misaligned implementations.
Step 1: Audit & Discovery
Before writing definitions, conduct a full audit:
- Review the provided terms (listed above in $ARGUMENTS)
- Scan the codebase for:
- Component names that imply domain concepts (e.g.,
CommitWeekModal,BundleEditor) - State variables with domain meaning (e.g.,
isCommitted,editorMode) - Comments or docs referencing undefined jargon
- Component names that imply domain concepts (e.g.,
- Identify gaps - Ask me clarifying questions for any term that is:
- Ambiguous
- Has multiple possible interpretations
- References UI/UX states not fully described
Output a list of all discovered terms before proceeding. Wait for my confirmation before writing the dictionary.
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.
- 4d ago First seen · 181 lines · 10 tokens per session scan A ba7d6ab9cd46
define-terms is a command published in the GitHub repository VishalJ99/claude-docker (188 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 1,335 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.