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 skills add alsk1992/CloddsBot --skill webhooksgit clone --depth 1 https://github.com/alsk1992/CloddsBotWrote 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/alsk1992/cloddsbot/webhooks)<a href="https://agentmods.dev/skills/alsk1992/cloddsbot/webhooks"><img src="https://agentmods.dev/badge/skills/alsk1992/cloddsbot/webhooks.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00012 | $0.00306 |
| Opus 5 | $0.00006 | $0.00153 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
webhooks 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 4d 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.
What it actually says
Webhooks
Register, manage, and inspect incoming webhook endpoints with optional HMAC-SHA256 signature verification.
Commands
/webhooks list - List all registered webhooks
/webhooks register <id> <path> - Register a webhook endpoint
/webhooks register <id> <path> --secret <key> - Register with HMAC secret
/webhooks unregister <id> - Remove a webhook
/webhooks enable <id> - Enable a webhook
/webhooks disable <id> - Disable a webhook
/webhooks get <id> - View webhook details
Examples
/webhooks list
/webhooks register trade-signals /hooks/trades
/webhooks register alerts /hooks/alerts --secret mysecretkey
/webhooks get trade-signals
/webhooks disable trade-signals
/webhooks enable trade-signals
/webhooks unregister trade-signals
Webhook Details
The /webhooks get <id> command shows:
- Path the webhook listens on
- Description (if set)
- Enabled/disabled status
- Whether an HMAC secret is configured
- Total trigger count
Security
Webhooks support HMAC-SHA256 payload verification. Pass --secret <key> when registering to enable signature validation on incoming requests.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 50 lines · 12 tokens per session scan A 91e7732c7e45
webhooks is a skill published in the GitHub repository alsk1992/CloddsBot (895 stars, last pushed 6d ago), licensed MIT. It adds 12 tokens to every session and 306 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
hive-network-infrastructure
Use this skill when the user asks about chain state or transaction plumbing — gas prices, blocks, transaction receipts and status ("did my tx go through"), event logs, supported networks, fee data, or RPC diagnostics. Use it whenever the answer needs current chain-level evidence. For wallet holdings use…
aomi-build
Scaffold new Aomi apps and plugins from API docs, OpenAPI/Swagger specs, or SDK references. aomi-build generates production-ready Rust SDK crates (lib.rs, client.rs, tool.rs) with tool schemas, preambles, host-interop flows, and validation — turning a vendor's API surface into AI-agent-callable tools. It covers the…
hive-build
Use this skill when the user is integrating Hive into application code, backend services, agents, cron jobs, source-controlled adapters, or production systems — wiring Hive into a Next.js API route, a Python or Go cron job, a Rust or Java service, or a LangChain/CrewAI agent — rather than asking a one-off chat query.
emblem-ai
One-shot user management for apps, multi-chain wallet authentication, an AI-powered assistant, and AI app introspection. Use when the user wants to let website users sign in with wallets, email/password, or social login and give each user a wallet-enabled account, then embed EmblemAI chat surfaces, connect plugins, or…
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.