agentmods.dev

dc-ntfy

A command for sending plain or formatted notifications to Discord through a webhook, a URL that accepts messages from other services.

In plain words
What is it for?
Use it to send text or embeds, choose a named webhook target, add fields, or apply a colour preset.
Why use it?
It turns common notification options into one command and uses configured webhook settings to deliver the message.

Command

2 2d ago A scan 23 tokens original MIT
View the source file musingfox/cc-plugins
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/musingfox/cc-plugins/dc-ntfy
Clone the repo
git clone --depth 1 https://github.com/musingfox/cc-plugins
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 492 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00023 $0.00492
Opus 5 $0.00012 $0.00246
Sonnet 5 $0.00005 $0.00098
Haiku 4.5 $0.00002 $0.00049

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

Security

Grade A, and why

dc-ntfy scanned grade A 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

3. **Send** — POST to the resolved webhook URL using `curl`. Handle response per discord-webhook skill guidance.
discord-webhook/commands/dc-ntfy.md · 43 lines

What it actually says

Discord Notify

Send a notification to a Discord channel via webhook.

Arguments

Parse the user's arguments to determine message format:

  • Plain text: /dc-ntfy "Deploy complete" → send as content
  • Embed with title: /dc-ntfy --embed "Title" "Description" → send as Embed
  • Named target: /dc-ntfy --to deploy "message" → send to DISCORD_WEBHOOK_DEPLOY
  • Embed with fields: /dc-ntfy --embed "Title" "Desc" --field "Key" "Value" → Embed with fields
  • Color override: /dc-ntfy --color success "message" → apply color preset

If no arguments are provided, ask the user what message to send.

Execution

Follow the discord-webhook skill workflow for webhook URL resolution, payload formatting, and sending:

  1. Resolve webhook URL — source .env if it exists ([ -f .env ] && source .env), then resolve the named webhook if --to {name} is specified, otherwise use default. See the discord-webhook skill for details.

  2. Build payload — based on parsed arguments:

    • No --embed flag → plain text content payload
    • With --embed → Embed payload with title, description, optional fields
    • Apply --color preset if specified: success → 3066993, error → 15158332, warning → 15105570, info → 3447003 (default)
    • Use jq for safe JSON construction (see discord-webhook skill for details)

  3. Send — POST to the resolved webhook URL using curl. Handle response per discord-webhook skill guidance.

  4. Report result — keep output concise:

    • 204 → "Discord notification sent."
    • 4xx → report error with status code and guidance
    • 429 → report rate limit, suggest waiting
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 · 43 lines · 0 tokens per session scan A c399e350251e

Subscribe to this mod's changes

dc-ntfy is a command published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 492 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens