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/n9e/fe/cmtgit clone --depth 1 https://github.com/n9e/feWhat 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.00057 | $0.01506 |
| Opus 5 | $0.00028 | $0.00753 |
| Sonnet 5 | $0.00011 | $0.00301 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
cmt 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 today.
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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cmt — Git Review & Commit
Override: This skill replaces the default system commit workflow when
/cmtis invoked. Follow this skill exactly.
When the user invokes /cmt [mode], prepare a conventional commit for current git changes.
| Command | Mode | Behavior |
|---|---|---|
/cmt |
fast |
Default. Inspect changes, run git diff --check, show summary, wait for approval. |
/cmt fast |
fast |
Same as default. |
/cmt strict |
strict |
Simplify safely, run full review, verify, wait for approval. |
Unknown modes: stop and list fast and strict.
Workflow
1. Parse Mode And Check Status
Default to fast when no mode is provided.
git branch --show-current
git status --short --branch
Identify:
- current branch
- staged files
- unstaged changes
- untracked files
- merge conflicts
Stop if:
- working tree is clean → report "Nothing to commit"
- merge conflicts are present → report conflicts
- only untracked files with unclear purpose → ask before staging
Branch policy:
mainormaster: always require extra-clear confirmation before commit.- Feature branches (
feat*): proceed through the selected mode, but still require explicit user approval. - Other branches: use judgment; ask briefly if unclear.
If unrelated changes are mixed together, ask what to include before proceeding.
2. Inspect Current Changes
For staged changes:
git diff --staged
For unstaged changes:
git diff
Focus on:
- correctness and regressions
- accidental debug code, secrets, generated noise, or unrelated churn
- whether the change should be split into separate commits
If there are unstaged changes that belong to the same task, include them. If unrelated, ask before staging.
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.
- today First seen · 229 lines · 57 tokens per session scan A 1e19d16b5b97
cmt is a command published in the GitHub repository n9e/fe (302 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 1,506 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-09-01.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.