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/new1direction/korgex/handling-webhooksnpx skills add New1Direction/korgex --skill handling-webhooksgit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/handling-webhooks)<a href="https://agentmods.dev/skills/new1direction/korgex/handling-webhooks"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/handling-webhooks.svg" alt="Measured on agentmods" 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.00011 | $0.00351 |
| Opus 5 | $0.00005 | $0.00176 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
handling-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 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.
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
A webhook is an untrusted HTTP request from an external system announcing an event. Treat the endpoint as a public, hostile-input surface.
- Verify authenticity. Validate the provider's signature (HMAC over the raw body with the shared secret) before trusting anything. Reject unsigned/invalid requests. Compare signatures in constant time.
- Use the RAW body for verification. Don't parse-then-reverify — signatures are over exact bytes; re-serialized JSON won't match.
- Respond fast, work async. Acknowledge quickly (2xx) and do the real work on a queue (see designing-a-job-queue). Providers retry on slow/failed responses, so blocking work in the handler causes timeouts and duplicate deliveries.
- Expect duplicates + out-of-order. Webhooks are at-least-once. Dedupe on the event id and make handling idempotent; don't assume events arrive in order.
- Validate + scope the payload. It's untrusted input (see security-review) — validate shape, and never feed it unsanitized into a query/command/path.
- Return the right codes. 2xx = received (provider stops retrying); 4xx = won't accept (bad signature/payload); 5xx = transient, please retry. Don't 200 a request you failed to actually process.
- Log received event ids (not secrets) so you can reconcile missed/duplicate deliveries.
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 · 27 lines · 11 tokens per session scan A 01a96a0698e5
handling-webhooks is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 351 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-08-31.
Other skills, from other repositories
vibe-ui-design
Use when designing UI/UX, defining design systems, choosing color palettes, typography, spacing, or component primitives. Triggers on "design system", "design tokens", "color palette", "UI 设计", "深色工业风", "design language".
vibe-security
Use when performing security audits, vulnerability scanning, dependency checks, or secure code reviews. Triggers on "security audit", "scan vulnerabilities", "安全审查", "漏洞扫描", "OWASP", "dependency check".
vibe-ui-beautify
Use when adding animations, micro-interactions, 3D effects, glassmorphism, or "juicy" tactile feedback to UI components. Triggers on "animation", "hover effect", "transition", "动效", "果汁感", "Framer Motion", "GSAP", "3D 视效".
vibe-plan
Use this skill to create a phased development plan based on requirements, architecture, and API docs.
vibe-test
Use when writing tests, performing unit testing, integration testing, or verifying system functionality. Triggers on "write tests", "run tests", "add unit test", "TDD", "测试", "跑测试".
vibe-autopilot
Use this skill when the user requests fully autonomous, 24/7 hands-free development without human intervention.