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/musingfox/cc-plugins/discord-webhooknpx skills add musingfox/cc-plugins --skill discord-webhookgit clone --depth 1 https://github.com/musingfox/cc-pluginsWhat 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.00086 | $0.01187 |
| Opus 5 | $0.00043 | $0.00593 |
| Sonnet 5 | $0.00017 | $0.00237 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
Discord Webhook 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 via HTTP POST** using `curl` How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discord Webhook Notification
Send messages to Discord channels via webhook HTTP POST. Supports plain text and rich Embed format with multi-webhook routing.
Overview
Discord webhooks accept JSON payloads via HTTP POST. This skill handles:
- Resolve webhook URL from environment variables or settings file
- Format the message as plain text (
content) or rich Embed - Send via HTTP POST using
curl
Step 1: Resolve Webhook URL
Before resolving, source the project .env file if it exists:
[ -f .env ] && source .env
Then check environment variables:
1a: Named Webhook (when a target name is specified)
Look for environment variable DISCORD_WEBHOOK_{NAME} where {NAME} is the uppercase target name:
# Examples:
# Target "deploy" → DISCORD_WEBHOOK_DEPLOY
# Target "alerts" → DISCORD_WEBHOOK_ALERTS
1b: Default Webhook
Look for environment variable DISCORD_WEBHOOK_URL.
Error Handling
If no webhook URL is found, inform the user:
No Discord webhook URL configured. Add to your
.envfile:DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/your/webhookFor named targets, use
DISCORD_WEBHOOK_{NAME}(e.g.,DISCORD_WEBHOOK_DEPLOY).
Do NOT proceed without a valid webhook URL.
Step 2: Format the Message
Plain Text
For simple string messages, use the content field:
{
"content": "Deploy v1.2.3 completed successfully"
}
content has a 2000 character limit. Truncate with … if exceeded.
Embed Format
For structured information (deploy reports, error alerts, build status), use the embeds array:
{
"embeds": [{
"title": "Deploy Complete",
"description": "Version **v1.2.3** deployed to production",
"color": 3066993,
"fields": [
{ "name": "Environment", "value": "production", "inline": true },
{ "name": "Duration", "value": "2m 34s", "inline": true }
],
"footer": { "text": "Deployed by Claude Code" },
"timestamp": "2026-04-10T12:00:00.000Z"
}]
}
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.
- yesterday First seen · 156 lines · 86 tokens per session scan A e05c94ffd91f
Discord Webhook is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 1,187 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…