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/mylee04/code-notify/commitgit clone --depth 1 https://github.com/mylee04/code-notifyWhat 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.00006 | $0.00358 |
| Opus 5 | $0.00003 | $0.00179 |
| Sonnet 5 | $0.00001 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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 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
Commit Changes
What This Command Does
- Checks for uncommitted changes
- Runs tests to verify code works
- Generates appropriate commit message
- Creates the commit
When to Use
- After completing a feature or fix
- When changes are ready to be saved
Process
1. Pre-Commit Checks
# Run tests
make test
# Check for lint issues
shellcheck bin/code-notify lib/code-notify/**/*.sh
2. Review Changes
git status
git diff --stat
3. Commit Message Format
type: brief description
- Detail 1
- Detail 2
Types
| Type | Use For |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation |
| refactor | Code refactoring |
| test | Adding tests |
| chore | Maintenance |
4. Example Messages
feat: add WSL support for notifications
- Detect WSL environment via /proc/version
- Use wsl-notify-send.exe for Windows notifications
- Add setup wizard option to install wsl-notify-send
fix: handle non-git directories on Windows
- Wrap git commands in try-catch
- Check $LASTEXITCODE after git commands
- Fall back to folder name when not in git repo
Rules
- No Co-Authored-By lines
- No .env files
- Run tests before committing
- Keep messages concise but descriptive
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 · 82 lines · 6 tokens per session scan A 94c4563e3bb6
commit is a command published in the GitHub repository mylee04/code-notify (288 stars, last pushed 3d ago), licensed MIT. It adds 6 tokens to every session and 358 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.