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/test-notifygit 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.00005 | $0.00322 |
| Opus 5 | $0.00003 | $0.00161 |
| Sonnet 5 | $0.00001 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
test-notify 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
Test Notifications
What This Command Does
- Detects current platform (macOS/Linux/Windows/WSL)
- Checks for available notification tools
- Sends a test notification
- Verifies notification was delivered
When to Use
- After installation to verify setup
- When debugging notification issues
- Before releasing a new version
Process
1. Check Environment
make test
2. Send Test Notification
cn test
3. Verify Delivery
- Notification should appear in system tray/notification center
- Sound should play (if enabled)
- Check logs:
~/.claude/logs/notifications.log
Expected Results
| Platform | Tool | Notification Location |
|---|---|---|
| macOS | terminal-notifier | Notification Center |
| macOS | osascript | Notification Center |
| Linux | notify-send | Desktop notifications |
| Windows | BurntToast | Action Center |
| WSL | wsl-notify-send | Windows Action Center |
Troubleshooting
No notification appears
- Check if notification tool is installed
- Check system notification settings (Do Not Disturb, etc.)
- Run with debug:
DEBUG=1 cn test
Sound doesn't play
- Check system volume
- Verify sound file exists
- Check terminal-notifier version (macOS)
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 · 63 lines · 5 tokens per session scan A 149deae0494f
test-notify is a command published in the GitHub repository mylee04/code-notify (288 stars, last pushed 4d ago), licensed MIT. It adds 5 tokens to every session and 322 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.