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/easingthemes/dx-aem-flow/auto-webhooksnpx skills add easingthemes/dx-aem-flow --skill auto-webhooksgit clone --depth 1 https://github.com/easingthemes/dx-aem-flowWrote 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/easingthemes/dx-aem-flow/auto-webhooks)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/auto-webhooks"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/auto-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.00049 | $0.06262 |
| Opus 5 | $0.00024 | $0.03131 |
| Sonnet 5 | $0.00010 | $0.01252 |
| Haiku 4.5 | $0.00005 | $0.00626 |
Grade A, and why
auto-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 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.
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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You configure ADO service hooks and the PR Review build validation policy. ADO has no native az devops service-hooks CLI command — all REST calls use az rest (ADO PAT auth, audit-wrapped).
0. Prerequisites
Read .ai/automation/infra.json. Extract automationProfile.
source .ai/lib/audit.sh
export AUDIT_LOG_PREFIX=infra
Profile determines scope:
- Full hub: WI hooks (project-scoped) + PR Answer hook (repo-scoped) + PR Review build policy
- Consumer: PR Answer hook (repo-scoped) + PR Review build policy only. Consumers do NOT create WI hooks (hub owns those). Consumers DO need their own PR Answer hook and PR Review policy.
Extract:
adoOrg— ADO org URLadoProject— ADO project namepipelines.pr-review.id— PR Review pipeline ID (for build validation policy)pipelines.pr-answer.id— PR Answer pipeline ID (for registering with hub)- For full-hub only:
webhooks.wi-userstory.url(BugFix uses the Azure-nativewebhooks.bugfixcomment hook — see 2c — not a WI-Router URL) - Check if
webhooks.*.statusis alreadyconfigured— skip if so
For consumers: The PR Answer hook URL points to the hub's PR Router Lambda. Ask:
Hub's PR Router Lambda URL? The API Gateway URL from the hub project's infra.json (e.g.,
https://<id>.execute-api.us-east-1.amazonaws.com/prod/pr-answer).
Ask once for shared values needed for hooks:
Webhook username? (same as Lambda
BASIC_USERset in hub's/auto-lambda-env)
Webhook password? (same as Lambda
BASIC_PASS) — secret, not stored
Webhook secret? (same as Lambda
WEBHOOK_SECRET) — secret, not stored
Ask for ADO project ID (required by service hook API):
ADO project ID? Find in ADO > Project Settings > Overview > Project ID (GUID format). You can also run:
az devops project show --project "<adoProject>" --query id --output tsv
Get the repository ID for repo-scoped hooks:
REPO_ID=$(az repos show --repository "<repo-name>" --project "<adoProject>" --query id --output tsv)
Read scm.base-branch from .ai/config.yaml for branch filtering.
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 · 408 lines · 49 tokens per session scan A 71d0c9bbbebc
auto-webhooks is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 6,262 once invoked, about $0.0002 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
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
release-openclaw-plugin-testing
Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.