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/xiaolai/nlpm/vocab-initgit clone --depth 1 https://github.com/xiaolai/nlpmWrote 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/xiaolai/nlpm/vocab-init)<a href="https://agentmods.dev/commands/xiaolai/nlpm/vocab-init"><img src="https://agentmods.dev/badge/commands/xiaolai/nlpm/vocab-init.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.00056 | $0.02566 |
| Opus 5 | $0.00028 | $0.01283 |
| Sonnet 5 | $0.00011 | $0.00513 |
| Haiku 4.5 | $0.00006 | $0.00257 |
Grade A, and why
vocab-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 5d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Workflow
Step 1: Resolve target path
Parse $ARGUMENTS:
| Input | Behavior |
|---|---|
| (empty) | Target = current working directory |
| absolute path | Target = that path |
| relative path | Target = <cwd>/<path> |
If the target does not exist or is not a directory → "Target path not found: {path}". Stop.
Step 2: Detect plugin name
Read <target>/.claude-plugin/plugin.json if it exists. Use the name field.
If no manifest exists, use the basename of the target directory (e.g., /home/dev/my-project/ → my-project). Lowercase, replace spaces/underscores with hyphens.
Store as plugin_name for the rest of the workflow.
Step 3: Detect layout
Use Glob against the target path to check which of these patterns exist; build the scope config from what is present:
| Pattern | Scope | Role | Notes |
|---|---|---|---|
commands/*.md |
internal | verb-filename | Claude Code plugin commands |
agents/*.md |
internal | noun-filename | Claude Code plugin agents |
skills/*/*/SKILL.md |
internal | skill-dirname | Plugin-namespaced skills |
skills/*/SKILL.md |
internal | skill-dirname | Flat skill layout (no plugin namespace) |
.github/workflows/*.yml |
auditor | verb-filename | Auditor-style workflows; only emit this scope if at least 3 workflow files match auditor-* or similar pipeline naming |
hooks/hooks.json |
internal | (no extraction; presence-only) | Skip in scope config; just note in the skeleton |
docs/*.md |
internal | headings | Author/user docs |
analysis/*.md |
internal | headings | Design notes |
Only include scopes where at least one matching file exists. If only docs/ matches and nothing else, the project has too little NL surface for vocabulary discipline — stop with: "Target has minimal NL surface (only {N} files matched). Vocabulary discipline is premature here. Re-run /nlpm:vocab-init after the artifact set grows."
Step 4: Write the scope config
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.
- 5d ago First seen · 262 lines · 56 tokens per session scan A ff72a4a6463f
vocab-init is a command published in the GitHub repository xiaolai/nlpm (134 stars, last pushed yesterday), licensed ISC. It adds 56 tokens to every session and 2,566 once invoked, about $0.0003 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.