notify

A command that sends a sound, desktop banner, or optional phone vibration when something happens in a long workflow. It tries several notification methods, including macOS and Linux tools.

In plain words
What is it for?
It is for sending informational, success, or urgent messages with an optional title from scripts or other commands.
Why use it?
It helps you notice that a work chunk finished or that a decision needs your attention without watching the terminal.

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/martybonacci/specswarm/notify
Clone the repo
git clone --depth 1 https://github.com/MartyBonacci/specswarm
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,270 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00042 $0.01270
Opus 5 $0.00021 $0.00635
Sonnet 5 $0.00008 $0.00254
Haiku 4.5 $0.00004 $0.00127

Measured 3d ago against content hash 0be70d29eeee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

plugins/ss/commands/notify.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SpecSwarm Notify

Sends a notification using whatever mechanism is available — convocli-notifier plugin (preferred), then notify-send (Linux libnotify), then osascript (macOS), then a terminal bell + stderr message.

Project-agnostic — works on any project regardless of installed plugins. Silent no-op only if none of the four tiers is available, which is rare.

Fire the notification

PLUGIN_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
LIB="${PLUGIN_DIR}/lib/notify.sh"

if [ ! -f "$LIB" ]; then
  echo "❌ notify.sh helper not found at $LIB" >&2
  exit 2
fi

# Parse arguments
URGENCY="info"
TITLE="SpecSwarm"
MESSAGE=""

while [ $# -gt 0 ]; do
  case "$1" in
    --urgent) URGENCY="urgent"; shift ;;
    --success) URGENCY="success"; shift ;;
    --info) URGENCY="info"; shift ;;
    --title) TITLE="$2"; shift 2 ;;
    -h|--help)
      cat <<EOF
Usage: /ss:notify [--urgent|--success|--info] [--title TITLE] [MESSAGE]

Fires a notification using the best-available channel.

Examples:
  /ss:notify "P1.3 ready for review"
  /ss:notify --urgent "Build broke at T012"
  /ss:notify --success --title "Chunk shipped" "P1.3 merged to main"
EOF
      exit 0
      ;;
    *)
      if [ -z "$MESSAGE" ]; then
        MESSAGE="$1"
      else
        MESSAGE="$MESSAGE $1"
      fi
      shift
      ;;
  esac
done

# shellcheck disable=SC1090
source "$LIB"

if ! ss_notify_available; then
  echo "⚠️  No notification mechanism available. Falling back to terminal bell + stderr."
fi

if ss_notify "$URGENCY" "$TITLE" "$MESSAGE"; then
  echo "🔔 Notified [${URGENCY}] ${TITLE}: ${MESSAGE}"
else
  echo "(notification suppressed — debounced within last ${SS_NOTIFY_DEBOUNCE:-10}s)"
fi

Why this exists

The convocli-notifier plugin (when installed) already fires on every Claude Code Stop event — so you get a chime each time Claude finishes responding. That's the baseline.

/ss:notify adds semantic notifications on top: differentiated sounds for urgent/success/info, plus the ability to fire from inside a long-running workflow at a specific moment (e.g., midway through /ss:build when a strategic decision is needed).

Read the full file on GitHub · 136 lines

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. 3d ago First seen · 136 lines · 42 tokens per session scan A 0be70d29eeee

Subscribe to this mod's changes

notify is a command published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,270 once invoked, about $0.0002 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.