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/asana-webhooksnpx skills add hookdeck/webhook-skills --skill asana-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/asana-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/asana-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/asana-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.00061 | $0.01932 |
| Opus 5 | $0.00030 | $0.00966 |
| Sonnet 5 | $0.00012 | $0.00386 |
| Haiku 4.5 | $0.00006 | $0.00193 |
Grade A, and why
asana-webhooks scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://app.asana.com/api/1.0/webhooks \ This is a copy
83% identical to adyen-webhooks — 195 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Asana Webhooks
When to Use This Skill
- How do I receive Asana webhooks?
- How do I implement the Asana
X-Hook-Secrethandshake? - How do I verify Asana webhook signatures (
X-Hook-Signature)? - How do I handle task, project, or story events (
added,changed,removed,deleted,undeleted)? - Why is my Asana webhook signature verification failing?
How Asana Webhooks Work
Asana webhooks have two phases that both POST to your target URL:
- Handshake (once, at creation). When you call
POST /webhooks, Asana sends a request carrying anX-Hook-Secretheader and noX-Hook-Signature. Your endpoint must echo that sameX-Hook-Secretback as a response header and return200. Store the secret — it is the key for verifying every future delivery. This secret is shown only during the handshake. - Event deliveries (ongoing). Every later request carries an
X-Hook-Signatureheader — a hex HMAC-SHA256 of the raw request body, keyed with the stored secret. The body is a batch:{"events": [...]}. Heartbeats arrive as{"events": []}.
Verification (core)
Distinguish the handshake from a normal delivery by which header is present, then HMAC the raw body and compare timing-safe.
Node:
const crypto = require('crypto');
function verifyAsanaSignature(rawBody, signatureHeader, secret) {
if (!signatureHeader || !secret) return false;
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
try {
return crypto.timingSafeEqual(
Buffer.from(signatureHeader, 'hex'),
Buffer.from(expected, 'hex')
);
} catch {
return false; // wrong length / malformed hex
}
}
// Handshake: echo X-Hook-Secret, store it, return 200.
// Delivery: verifyAsanaSignature(rawBody, req.headers['x-hook-signature'], storedSecret)
Python:
import hmac, hashlib
def verify_asana_signature(raw_body: bytes, signature_header: str, secret: str) -> bool:
if not signature_header or not secret:
return False
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(signature_header, expected)
What ships with it
19 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 380 B
- examples/express/package.json 390 B
- examples/express/README.md 2.0 KB
- examples/express/src/index.js 4.2 KB runs code
- examples/express/test/webhook.test.js 5.1 KB runs code
- examples/fastapi/.env.example 340 B
- examples/fastapi/main.py 3.5 KB runs code
- examples/fastapi/README.md 2.0 KB
- examples/fastapi/requirements.txt 95 B
- examples/fastapi/test_webhook.py 5.1 KB runs code
- examples/nextjs/.env.example 340 B
- examples/nextjs/app/webhooks/asana/route.ts 3.6 KB runs code
- examples/nextjs/package.json 502 B
- examples/nextjs/README.md 1.9 KB
- examples/nextjs/test/webhook.test.ts 3.4 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.8 KB
- references/setup.md 4.0 KB
- references/verification.md 4.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.
- 4d ago First seen · 170 lines · 61 tokens per session scan A ab6b0d166ecd
asana-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,932 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 83% identical to adyen-webhooks, differing in 195 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…