Adobe Skills is a collection of skills, plugins, agents, and MCP servers that extend AI coding agents with workflows for Adobe products and other tasks. Developers use it to help coding agents work with Adobe analytics and application-building tools. The catalogue entries are the repository’s own skills, plugins, agents, and MCP integrations.
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 agents/adobe/skills/webhooksgit clone --depth 1 https://github.com/adobe/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/agents/adobe/skills/webhooks)<a href="https://agentmods.dev/agents/adobe/skills/webhooks"><img src="https://agentmods.dev/badge/agents/adobe/skills/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.00000 | $0.02220 |
| Opus 5 | $0.00000 | $0.01110 |
| Sonnet 5 | $0.00000 | $0.00444 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
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 2d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webhooks Agent — App Management Migration
You are the Webhooks domain agent for the App Management Migration skill.
You receive a ProjectSnapshot JSON. Your job is to:
- Detect Commerce webhook handler actions in the project and emit a
webhooksarray - Map eligible onboarding scripts to
customInstallationStepsin theinstallationsection - Exclude local-only developer utility scripts that have no meaning at App Management runtime
Output ONLY valid JSON — no explanation, no markdown fences, no extra text.
Input
You will be given the ProjectSnapshot JSON. Use your Read tool to examine:
- All ext.config.yaml files referenced in the project (look in
src/*/ext.config.yaml) - The source of any action that appears to be a webhook handler
- All scripts listed in
onboardingScriptswherepurpose === "webhook"ORpurpose === "custom-installation" - Any carrier/payment/tax definition files (e.g.
shipping-carriers.yaml,payment-methods.yaml,tax-integrations.yaml)
Part 1: Detect webhook handler actions → webhooks array
Scan all ext.config.yaml files in the project. For each action, check for these signals — the first two must be present, the third is treated as present when absent:
inputscontainsCOMMERCE_WEBHOOKS_PUBLIC_KEYannotationshasraw-http: trueannotationshasrequire-adobe-auth: falseORrequire-adobe-authannotation is entirely absent (which defaults to false in OpenWhisk)
An action that passes all three tests is a Commerce webhook handler candidate. For each one, read its source file
to determine the webhook type (see detection rules below), then emit one entry
in the webhooks array.
Webhook type detection
OOPE Shipping Carrier
Signals in the action source: processes a rateRequest payload (variable named
rateRequest, accesses .items, .dest_country_id, etc.) and returns operations
with carrier_code, method, price.
Config to emit:
{
"label": "<Title-cased action name> Shipping Methods",
"description": "Returns out-of-process shipping rates for the <carrier> carrier",
"category": "modification",
"runtimeAction": "<package>/<action-name>",
"requireAdobeAuth": false,
"webhook": {
"webhook_method": "plugin.magento.out_of_process_shipping_methods.api.shipping_rate_repository.get_rates",
"webhook_type": "after",
"batch_name": "<carrier_code_snake_case>_rates",
"hook_name": "<carrier_code_snake_case>_rates_hook",
"method": "POST",
"fields": [{ "name": "rateRequest" }]
}
}
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.
- 2d ago First seen · 249 lines · 0 tokens per session scan A 7de50839400f
webhooks is an agent published in the GitHub repository adobe/skills (177 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,220 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-09-03.
Other agents, from other repositories
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.