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/reviewgit 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.00292 |
| Opus 5 | $0.00003 | $0.00146 |
| Sonnet 5 | $0.00001 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
review 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
Code Review
What This Command Does
- Analyzes code for security issues
- Checks shell scripting best practices
- Verifies cross-platform compatibility
- Provides improvement suggestions
When to Use
- Before merging PRs
- After significant changes
- When adding new features
Process
1. Invoke Code Reviewer Agent
The code-reviewer agent will analyze:
- Security vulnerabilities
- Shell best practices
- Cross-platform compatibility
- Code quality
2. Review Areas
Security Checklist
- No hardcoded credentials
- Input sanitization
- No command injection risks
- Safe file handling
Best Practices
- Variables quoted
- Functions use local
- Error handling present
- Commands existence checked
Cross-Platform
- Works on macOS
- Works on Linux
- PowerShell equivalent correct
- WSL compatible
3. Output
Review generates a report with:
- Issues found (by severity)
- Specific line numbers
- Suggested fixes
- Overall verdict (APPROVE/NEEDS CHANGES/BLOCK)
Usage
Review the changes in lib/code-notify/core/notifier.sh
The code-reviewer agent will be invoked automatically.
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 · 70 lines · 5 tokens per session scan A 47593144f15f
review 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 292 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.