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/akeneo-webhooksnpx skills add hookdeck/webhook-skills --skill akeneo-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/akeneo-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/akeneo-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/akeneo-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.00071 | $0.01498 |
| Opus 5 | $0.00036 | $0.00749 |
| Sonnet 5 | $0.00014 | $0.00300 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
akeneo-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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Akeneo Webhooks
When to Use This Skill
- Setting up Akeneo PIM Events API webhook handlers
- Debugging
x-akeneo-request-signatureverification failures - Understanding Akeneo event types and the batched
eventspayload - Handling product and product-model created/updated/removed events
Verification (core)
Akeneo has no official SDK — verify manually. Each request carries two headers:
x-akeneo-request-signature— hex HMAC-SHA256x-akeneo-request-timestamp— Unix seconds
The signed content is timestamp + "." + rawBody. Compute the HMAC with your
connection secret and compare, timing-safe, against the header. Use the
raw request body — don't JSON.parse first. Reject stale requests
(now - timestamp > 300) to prevent replay.
const crypto = require('crypto');
function verifyAkeneoWebhook(rawBody, signature, timestamp, secret) {
if (!signature || !timestamp) return false;
const age = Math.floor(Date.now() / 1000) - Number(timestamp);
if (!Number.isFinite(age) || Math.abs(age) > 300) return false; // 5-min replay window
const expected = crypto
.createHmac('sha256', secret)
.update(`${timestamp}.`)
.update(rawBody) // Buffer or string of the RAW body
.digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(signature, 'hex'), Buffer.from(expected, 'hex'));
} catch {
return false; // length mismatch = invalid
}
}
Python equivalent: hmac.new(secret, f"{timestamp}.".encode() + raw_body, hashlib.sha256).hexdigest(), compared with hmac.compare_digest.
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
Akeneo delivers all event types to a single Request URL, so dispatch by
action server-side. Payloads are batched: a top-level events array with
up to 10 events per request.
Event (action) |
Triggered When |
|---|---|
product.created |
A product is created |
product.updated |
A product is updated |
product.removed |
A product is deleted |
product_model.created |
A product model is created |
product_model.updated |
A product model is updated |
product_model.removed |
A product model is deleted |
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 242 B
- examples/express/package.json 368 B
- examples/express/README.md 1.5 KB
- examples/express/src/index.js 4.2 KB runs code
- examples/express/test/webhook.test.js 6.2 KB runs code
- examples/fastapi/.env.example 173 B
- examples/fastapi/main.py 3.5 KB runs code
- examples/fastapi/README.md 1.8 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 6.5 KB runs code
- examples/nextjs/.env.example 173 B
- examples/nextjs/app/webhooks/akeneo/route.ts 3.6 KB runs code
- examples/nextjs/package.json 480 B
- examples/nextjs/README.md 1.5 KB
- examples/nextjs/test/webhook.test.ts 4.1 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.4 KB
- references/setup.md 2.4 KB
- references/verification.md 3.8 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 · 132 lines · 71 tokens per session scan A 671285740304
akeneo-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,498 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.
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…