Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ApurvBazari/claude-plugins/plugin install 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/skills/apurvbazari/claude-plugins/setup)<a href="https://agentmods.dev/skills/apurvbazari/claude-plugins/setup"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/apurvbazari/claude-plugins/setup"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.02898 |
| Opus 5.5 | $0.00018 | $0.01159 |
| Sonnet 5.5 | $0.00009 | $0.00580 |
| Haiku 4.5 | $0.00004 | $0.00290 |
Grade A, and why
setup 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 1mo 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Skill — Notification Setup
You are running the notify setup skill. This installs and configures system notifications for Claude Code. Supports macOS (terminal-notifier) and Linux (notify-send).
Overview
Tell the developer:
Starting notify setup — I'll check dependencies, walk you through notification preferences, and configure hooks so you get native system notifications when Claude completes tasks or needs your attention.
Dry-Run Mode
If the user includes "dry-run" or "--dry-run" in their command arguments:
- Run all steps normally (dependency check, scope selection, customization)
- At Step 6 (Generate Artifacts), instead of writing files, display what would be written:
- Show the
notify.shscript content - Show the hook entries that would be merged into
settings.json - Show the
notify-config.jsoncontent
- Show the
- Skip Step 7 (Test) and Step 8 (Handoff)
- End with: "Dry run complete — no files were written. Re-run without
--dry-runto apply."
Step 1: Detect Platform & Check Dependencies
Run uname -s to detect the platform.
macOS (Darwin):
Run command -v terminal-notifier via Bash.
- If installed:
terminal-notifier is installed. Good to go. - If missing: offer to install via
${CLAUDE_PLUGIN_ROOT}/scripts/install-notifier.sh. If Homebrew is also missing, show install instructions and stop.
Linux:
Run command -v notify-send via Bash.
- If installed:
notify-send is available. Good to go. - If missing: show installation instructions from
${CLAUDE_PLUGIN_ROOT}/scripts/install-notifier.shoutput (distro-specificapt/dnf/pacmancommands) and stop.
Note: On Linux, sounds are not supported (mapped to urgency levels) and click-to-focus (activate) is not available. Inform the developer of these differences.
Step 2: Choose Install Scope
Ask the developer to choose an install scope:
Where should notifications be configured?
- Global (default) — Notifications for all projects (
~/.claude/)- This project only — Notifications scoped to this project directory (
$PWD/.claude/)
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.
- 1mo ago First seen · 303 lines · 44 tokens per session scan A acd44775c6e4
setup is a skill published in the GitHub repository ApurvBazari/claude-plugins (1 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 2,898 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
c-notify
Send native macOS notification center alerts from the command line using terminal-notifier.
notifications
Send notifications through the unified notification router.
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
agenticx-query-data-source
Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.