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 JansenAnalytics/claudex --skill webhook-receivergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/webhook-receiver)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/webhook-receiver"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/webhook-receiver/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/jansenanalytics/claudex/webhook-receiver"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/webhook-receiver.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.00091 | $0.00860 |
| Opus 5 | $0.00046 | $0.00430 |
| Sonnet 5 | $0.00018 | $0.00172 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade B, and why
webhook-receiver scanned grade B with 2 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 5d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST -d '{"hello":"world"}' http://127.0.0.1:9876/ping Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST -d '{"hello":"world"}' http://127.0.0.1:9876/ping How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webhook Receiver
A persistent Node.js HTTP server that listens for incoming POST requests, validates optional HMAC-SHA256 signatures, and executes shell commands per route.
Project location: ${WEBHOOK_RECEIVER_HOME:-$HOME/projects/webhook-receiver}/
Config: ${WEBHOOK_RECEIVER_HOME:-$HOME/projects/webhook-receiver}/config.json (live-reloaded, no restart needed)
Log: ${WEBHOOK_RECEIVER_HOME:-$HOME/projects/webhook-receiver}/logs/webhook.log
Port: 9876 (localhost only — expose via nginx/ngrok/Tailscale for real webhooks)
Start / Stop / Status
# Start
bash ${CLAUDE_SKILLS_DIR:-$HOME/.claude-agent/.claude/skills}/webhook-receiver/scripts/start.sh
# Stop
bash ${CLAUDE_SKILLS_DIR:-$HOME/.claude-agent/.claude/skills}/webhook-receiver/scripts/stop.sh
# Status + recent log
bash ${CLAUDE_SKILLS_DIR:-$HOME/.claude-agent/.claude/skills}/webhook-receiver/scripts/status.sh
Adding a Route
Edit ${WEBHOOK_RECEIVER_HOME:-$HOME/projects/webhook-receiver}/config.json directly — changes take effect immediately, no restart:
{
"routes": [
{
"path": "/github",
"secret": "your-github-webhook-secret",
"command": "bash $HOME/scripts/handle-github.sh",
"description": "GitHub events"
},
{
"path": "/ping",
"secret": "",
"command": "",
"description": "Health check"
}
]
}
Testing
# Test the ping route (always returns 200)
curl -X POST -d '{"hello":"world"}' http://127.0.0.1:9876/ping
# Test with GitHub-style signature
SECRET="mysecret"
BODY='{"action":"push"}'
SIG="sha256=$(echo -n "$BODY" | openssl dgst -sha256 -hmac "$SECRET" | cut -d' ' -f2)"
curl -X POST \
-H "X-Hub-Signature-256: $SIG" \
-H "Content-Type: application/json" \
-d "$BODY" \
http://127.0.0.1:9876/github
Command Environment Variables
Commands receive:
| Variable | Contents |
|---|---|
WEBHOOK_ROUTE |
URL path (e.g. /github) |
WEBHOOK_BODY |
Raw request body |
WEBHOOK_HEADERS |
All headers as JSON |
WEBHOOK_IP |
Sender IP |
What ships with it
5 files 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.
- 5d ago First seen · 114 lines · 91 tokens per session scan B 8cf0e0ecfdbc
webhook-receiver is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 860 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
Kafka Event-Driven Testing
Test Kafka-based event-driven systems, producer and consumer integration tests with Testcontainers, schema compatibility gates, idempotency and ordering verification, dead-letter handling, and end-to-end event flow assertions.
architecture-paradigm-event-driven
Applies event-driven async messaging to decouple producers and consumers. Use when designing real-time or multi-subscriber systems needing loose coupling.
architecture-paradigm-serverless
Applies serverless FaaS patterns for event-driven workloads. Use when designing bursty workloads with minimal infrastructure and pay-per-execution cost model.
architecture-patterns
Software architecture patterns and best practices.
azure-event-grid-webhooks
Receive and validate Azure Event Grid webhook deliveries. Use when setting up an Event Grid WebHook event handler, implementing the Microsoft.EventGrid.SubscriptionValidationEvent handshake (echo data.validationCode as validationResponse with HTTP 200), implementing the CloudEvents v1.0 HTTP OPTIONS abuse-protection…