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/aayushostwal/nexus/commit-messagegit clone --depth 1 https://github.com/aayushostwal/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.00011 | $0.00180 |
| Opus 5 | $0.00005 | $0.00090 |
| Sonnet 5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
commit-message 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 yesterday.
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
Draft a commit message for the currently staged changes.
Steps:
- Run
git diff --staged. If empty, rungit status --shortand tell the user nothing is staged — stop. - Summarize the diff into a Conventional Commit:
type(scope): summary. - Use
typefrom:feat,fix,refactor,docs,test,chore,perf,build,ci. - Keep the summary line under 72 chars, imperative mood, no trailing period.
- Add a short body only if the diff spans multiple concerns — bullet the key changes.
- Never add a co-author line or attribute the commit to an AI tool.
Output:
Outcome:
Message:
Next Step:
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.
- yesterday First seen · 23 lines · 11 tokens per session scan A a040261b87bf
commit-message is a command published in the GitHub repository aayushostwal/nexus (18 stars, last pushed 22d ago), licensed MIT. It adds 11 tokens to every session and 180 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
checkpoint
Full memory flush — refresh state.md, append to activity log, route any new decisions/insights, then commit and push.
log-decision
Add a new decision to the decisions log.
project-status
Summarize the current state of this client project.
eval-ai
Run Alcove's AI quality eval across smoke, real integrations, and agent-facing flows.
smoke-real-integrations
Run Alcove's high-cost real external integration smoke.
smoke
Run Alcove's isolated local smoke suite.