notify-setup

A setup command for notifications when Claude Code stops. The description includes setup, checking, and guidance for already-configured or unconfigured systems.

In plain words
What is it for?
It is for setting up stop notifications, checking whether they work, and explaining the setup status.
Why use it?
It helps users configure and verify stop notifications instead of checking the setup manually.

Command

Install

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.

agentmods
npx agentmods add commands/no-problem-dev/claude-code-plugins/notify-setup
Clone the repo
git clone --depth 1 https://github.com/no-problem-dev/claude-code-plugins
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 451 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00451
Opus 5 $0.00007 $0.00226
Sonnet 5 $0.00003 $0.00090
Haiku 4.5 $0.00001 $0.00045

Measured yesterday against content hash 8eece5007b2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

notify-setup 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 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. `~/.claude/settings.json` を読み取り、現在の `env` セクションの設定を確認
plugins/notify-on-stop/commands/notify-setup.md · 66 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 66 lines · 14 tokens per session scan B 8eece5007b2f

Subscribe to this mod's changes

notify-setup is a command published in the GitHub repository no-problem-dev/claude-code-plugins (5 stars, last pushed 5mo ago), with no licence file. It adds 14 tokens to every session and 451 once invoked, about $0.0001 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.