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 skills/rlajous/claude-code-commands/notificationsnpx skills add rlajous/claude-code-commands --skill notificationsgit clone --depth 1 https://github.com/rlajous/claude-code-commandsWrote 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/skills/rlajous/claude-code-commands/notifications)<a href="https://agentmods.dev/skills/rlajous/claude-code-commands/notifications"><img src="https://agentmods.dev/badge/skills/rlajous/claude-code-commands/notifications.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.00059 | $0.00596 |
| Opus 5 | $0.00030 | $0.00298 |
| Sonnet 5 | $0.00012 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
notifications 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Notifications
Resolve {SKILL_DIR} to the absolute, physical directory containing this loaded SKILL.md. If the
host cannot expose the path, use PLUGIN_ROOT, then CLAUDE_PLUGIN_ROOT, only to locate
skills/notifications/SKILL.md. Verify every requested resource exists. Never substitute an empty
variable or silently fall back to /scripts.
Commands
--doctor→ runbash "{SKILL_DIR}/scripts/notification-tools.sh" --doctor, report the output, and exit. The check must not query pull requests, create state, or emit a desktop notification.--daemon-command→ runbash "{SKILL_DIR}/scripts/notification-tools.sh" --daemon-command, print the absolute command unchanged, and exit.- No argument → show the resolved configuration with
python3 "{SKILL_DIR}/scripts/notification_config.py", explain which channels are enabled, and print the daemon command when PR activity or review requests are enabled.
The daemon is required for GitHub activity. Agent-complete notifications use the plugin's Stop
hook and do not require the daemon.
Configuration
Read .git-workflow/config.yaml, then the legacy .claude/config.yaml fallback:
notifications:
agentComplete: false
prActivity: false
sound: Glass
Both channels are opt-in. notifications.sound applies to all Git Workflow notifications. When it
is absent, accept reviewWatch.sound as a compatibility fallback, then use Glass.
Expected events
Agent completion announces only the main turn. Do not add SubagentStop or failure alerts. GitHub
activity announces submitted APPROVED, CHANGES_REQUESTED, and COMMENTED reviews on open PRs
authored by the authenticated user. General PR comments, CI, merges, dismissals, and commits are
outside this workflow.
Notification failures are best effort and must never fail a turn or review workflow. Do not read or
persist full transcripts; the completion adapter uses only the first useful line of
last_assistant_message and stores only a deduplication digest.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 58 lines · 59 tokens per session scan A 8022e4f77fc8
notifications is a skill published in the GitHub repository rlajous/claude-code-commands (30 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 596 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…