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/dz1922/claude-notify/statusgit clone --depth 1 https://github.com/dz1922/claude-notifyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/dz1922/claude-notify/status)<a href="https://agentmods.dev/commands/dz1922/claude-notify/status"><img src="https://agentmods.dev/badge/commands/dz1922/claude-notify/status.svg" alt="Measured on agentmods" height="20"></a>What 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.00332 |
| Opus 5 | $0.00003 | $0.00166 |
| Sonnet 5 | $0.00001 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade B, and why
status scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Read `~/.claude/settings.json` and display the current notification configuration. What it actually says
Notification Status
Read ~/.claude/settings.json and display the current notification configuration.
What to Show
- Enabled channels: Read
env.NOTIFY_CHANNELS(default: "desktop") - Hook events: List which events are wired (SubagentStop, TaskCompleted, Notification, Stop, StopFailure)
- Channel credentials status (show set/not set, mask actual values):
- Telegram: token and chat ID
- Slack: webhook URL
- Teams: webhook URL
- Lark: webhook URL
- Custom webhook: URL
- Optional settings:
- Sound:
env.NOTIFY_SOUND(default: Glass) - Quiet hours:
env.NOTIFY_QUIET_HOURS
- Sound:
Output Format
notify status
──────────────
Channels: desktop, telegram
Events: SubagentStop, TaskCompleted, Notification, Stop, StopFailure
Desktop: ✓ enabled
Telegram: ✓ token=bot***...*** chat=12***89
Slack: ✗ not configured
Teams: ✗ not configured
Lark: ✗ not configured
Webhook: ✗ not configured
Sound: Glass
Quiet: 22:00-08:00
Mask credentials: show first 3 and last 2 characters only, with ***...*** in between.
If a channel is listed in NOTIFY_CHANNELS but credentials are missing, show a warning.
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.
- 3d ago First seen · 45 lines · 7 tokens per session scan B 1f560df9dbfd
status is a command published in the GitHub repository dz1922/claude-notify (1 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 332 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
slack-sync
Refresh the Slack workspace reference cache (users, channels) with current data from the Slack API.
voice-status
Show effective voice + notification state, mute, and per-layer breakdown.
voice-mute
Time-bound mute for both voice + notifications (default 30m). --global for user scope.
voice-test
Fire a test "Claude ready" + "Claude waiting" so you can verify sound, voice, and notifications.
voice-off
Disable voice announcements (project scope by default; --global for user scope).
voice-on
Enable voice announcements (project scope by default; --global for user scope).