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/hookdeck/webhook-skills/aws-sns-webhooksnpx skills add hookdeck/webhook-skills --skill aws-sns-webhooksgit clone --depth 1 https://github.com/hookdeck/webhook-skillsWrote 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/hookdeck/webhook-skills/aws-sns-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/aws-sns-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/aws-sns-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 | $0.00074 | $0.01653 |
| Opus 5 | $0.00037 | $0.00826 |
| Sonnet 5 | $0.00015 | $0.00331 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
aws-sns-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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS SNS Webhooks
When to Use This Skill
- How do I receive AWS SNS messages at an HTTP/HTTPS endpoint?
- How do I confirm an SNS subscription (SubscriptionConfirmation / SubscribeURL)?
- How do I verify an SNS message signature?
- Why is my SNS signature verification failing?
- How do I handle SNS
NotificationandUnsubscribeConfirmationmessages?
How SNS Delivery Differs From HMAC Webhooks
SNS is not a Standard Webhooks / shared-secret HMAC provider. Instead:
- SNS POSTs a JSON envelope with
Content-Type: text/plain. Thex-amz-sns-message-typeheader tells you the type without parsing the body:SubscriptionConfirmation,Notification, orUnsubscribeConfirmation. - Authenticity is proven with an RSA signature over specific envelope fields
(not the raw body, and not an HMAC). You fetch AWS's public X.509
certificate from
SigningCertURLand RSA-verify the base64Signature. - New HTTP subscriptions require a handshake: the first message is a
SubscriptionConfirmation— you must GET itsSubscribeURL(or callConfirmSubscriptionwithToken) before SNS sends any notifications.
Verification (core)
Node ships the AWS-official sns-validator
(handles SigV1/SigV2, the sns.*.amazonaws.com cert-host check, cert fetch, and
RSA verify). Pass the parsed message object:
const MessageValidator = require('sns-validator');
const validator = new MessageValidator(); // defaults enforce sns.<region>.amazonaws.com certs over HTTPS
// message = JSON.parse(rawBody). SNS signs specific envelope fields, not the raw body.
validator.validate(message, (err, msg) => {
if (err) return res.status(400).send('Invalid signature');
// msg is verified. Branch on msg.Type / the x-amz-sns-message-type header.
});
Python has no AWS webhook SDK — verify manually. Build the canonical string in
byte-sorted field order, one Key\nValue\n pair per field that is present
(Message, MessageId, Subject?, Timestamp, TopicArn, Type for a
Notification; add SubscribeURL and Token for a SubscriptionConfirmation),
then RSA-verify with the cert from SigningCertURL (SHA1 for SignatureVersion
1, SHA256 for 2). See references/verification.md
(includes the UnsubscribeConfirmation field-set nuance).
What ships with it
20 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.
- examples/express/.env.example 294 B
- examples/express/package.json 425 B
- examples/express/README.md 2.2 KB
- examples/express/src/index.js 3.8 KB runs code
- examples/express/test/webhook.test.js 8.8 KB runs code
- examples/fastapi/.env.example 254 B
- examples/fastapi/main.py 5.6 KB runs code
- examples/fastapi/README.md 2.4 KB
- examples/fastapi/requirements.txt 114 B
- examples/fastapi/test_webhook.py 8.2 KB runs code
- examples/nextjs/.env.example 254 B
- examples/nextjs/app/webhooks/aws-sns/route.ts 3.7 KB runs code
- examples/nextjs/package.json 537 B
- examples/nextjs/README.md 2.3 KB
- examples/nextjs/test/webhook.test.ts 8.7 KB runs code
- examples/nextjs/tsconfig.json 404 B
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.2 KB
- references/setup.md 3.8 KB
- references/verification.md 7.4 KB
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 · 135 lines · 74 tokens per session scan A 8998f5c13db1
aws-sns-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 1,653 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…