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/validategit 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.00007 | $0.00334 |
| Opus 5 | $0.00003 | $0.00167 |
| Sonnet 5 | $0.00001 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
validate 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
Validate Scripts
What This Command Does
- Runs shellcheck on all .sh files
- Validates PowerShell syntax on .ps1 files
- Checks for common issues
- Reports findings
When to Use
- Before committing changes
- After refactoring code
- During code review
Process
1. Run Shellcheck
shellcheck bin/code-notify lib/code-notify/**/*.sh
2. Check PowerShell Syntax
# In PowerShell
$null = [System.Management.Automation.Language.Parser]::ParseFile(
"scripts/install-windows.ps1",
[ref]$null,
[ref]$errors
)
if ($errors) { $errors | ForEach-Object { Write-Error $_ } }
3. Run Tests
make test
Common Issues to Check
Shell Scripts
- Unquoted variables
- Missing
localin functions - Using
[ ]instead of[[ ]] - Missing error handling
- Undefined variables
PowerShell
- Missing error handling
- Unhandled exceptions
- Incorrect parameter types
- Missing -ErrorAction
Fix Common Issues
Unquoted Variables
# Before
echo $message
# After
echo "$message"
Missing Local
# Before
my_func() {
result="value"
}
# After
my_func() {
local result="value"
}
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 · 88 lines · 7 tokens per session scan A bd1d9564e646
validate is a command published in the GitHub repository mylee04/code-notify (288 stars, last pushed 3d ago), licensed MIT. It adds 7 tokens to every session and 334 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.