Borrowing it
Nothing to install: this file belongs to rudraptpsingh/axon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rudraptpsingh/axon/master/.claude/commands/webhook-test.mdgit clone --depth 1 https://github.com/rudraptpsingh/axonWrote 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/commands/rudraptpsingh/axon/webhook-test)<a href="https://agentmods.dev/commands/rudraptpsingh/axon/webhook-test"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/webhook-test/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/commands/rudraptpsingh/axon/webhook-test"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/webhook-test.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.00000 | $0.00078 |
| Opus 5.5 | $0.00000 | $0.00031 |
| Sonnet 5.5 | $0.00000 | $0.00016 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
webhook-test 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 2mo 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
Test alert webhook delivery end-to-end.
Run: bash scripts/e2e-webhook-config-file.sh
Report:
- Were webhook POSTs received by the test receiver?
- How many alerts fired and what types?
- Alert severities seen (warn / critical / resolved)
- Did axon serve exit cleanly?
- Any delivery failures, timeouts, or dropped webhooks?
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.
- 2mo ago First seen · 11 lines · 0 tokens per session scan A cb1673196413
webhook-test is a command published in the GitHub repository rudraptpsingh/axon (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 78 tokens. 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-31.
Other commands, from other repositories
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
api-runtime-verify
Verify a built backend HTTP surface at runtime: per route, record the response, assert it against the slice's acceptance behavior, and decide PASS/FAIL/BLOCKED. Do not use to review a contract before implementation (use api-contract-review or graphql-contract-review), write code (use implement-approved-slice), triage…
runtime-validate
Validate actual runtime behavior of HTTP APIs through execution testing. Tests GET endpoints, verifies responses match documentation, and catches functional failures.
state-validate
Validate stateful workflows and multi-step interactions. Tests authentication flows, shopping carts, pagination, session management, and state transitions through actual request sequences.
test
Generate API integration tests for endpoints.
run-load-test
Run API load tests with k6, Artillery, or Gatling to measure performance under load.