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/jsk9999/ai-nexus/commitgit clone --depth 1 https://github.com/JSK9999/ai-nexusWhat 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.00007 | $0.00136 |
| Opus 5 | $0.00003 | $0.00068 |
| Sonnet 5 | $0.00001 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
commit 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.
What it actually says
/commit
Create a git commit following conventional commit format.
Format
<type>(<scope>): <subject>
<body>
<footer>
Types
feat: New featurefix: Bug fixdocs: Documentationstyle: Formattingrefactor: Code refactoringtest: Testschore: Maintenance
Rules
- Subject line ≤ 50 characters
- Body wrapped at 72 characters
- Use imperative mood ("add" not "added")
- Reference issues in footer
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 · 35 lines · 7 tokens per session scan A 73724c750bfc
commit is a command published in the GitHub repository JSK9999/ai-nexus (18 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 136 once invoked, about $0.0000 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
commit
Create an atomic commit for current changes.
matcha:status
🍵 Master session health dashboard — intensity, git diff stats, test status, and marker ledger.
commit-msg
Cursor tooling: skills, rules, subagents.
triage
Confirm whether the work item still names real current work, choose the kind of reasoning owed next, and stop. Write the decisive evidence and handoff to $ARTIFACTSDIR/triage.md. You assess and route only: the repository must be exactly as you found it when you finish. No one watches the run; the report and your…
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.