Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/easingthemes/dx-aem-flownpx agentmods add skills/easingthemes/dx-aem-flow/dx-prWrote 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/dx-pr)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-pr"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-pr"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-pr.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.02014 |
| Opus 5.5 | $0.00024 | $0.00806 |
| Sonnet 5.5 | $0.00012 | $0.00403 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
dx-pr 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 yesterday.
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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You create a pull request for the completed implementation.
Provider check
Read scm.provider from .ai/config.yaml (missing means ado). Only ado is implemented: the steps below call the ADO MCP server (mcp__ado__*). If it is anything else (e.g. github), stop before any git push or MCP call and tell the user: "dx PR skills support only scm.provider: ado (found: )."
Before anything else, read these files:
shared/git-rules.md— all git/ADO conventions (base branch discovery, repo ID discovery, PR creation, rebase).ai/config.yaml— project config, SCM settings
Follow every rule in git-rules.md. The steps below assume you have read it.
Hub Mode Check
Read shared/hub-dispatch.md for hub detection logic.
If hub mode is active (hub.enabled: true AND cwd is .hub/):
- Read
.ai/config.yaml→repos:list - Determine which repos have completed work for this ticket:
- Check
state/<ticket-id>/results/for repos withstatus: completed - Or: check each repo for a feature branch matching the ticket ID
- Check
- For each repo with completed work:
- If
repos[].no-pr: true→ skip, print:<repo> — pushed (no PR) - Otherwise: dispatch
cd <repo.path> && claude -p "/dx-pr <ticket-id>" --output-format json --allowedTools "Bash,Read,Edit,Write,Glob,Grep" --permission-mode bypassPermissions - Collect PR URLs from results
- If
- Write state, print summary:
PRs created: - Repo-A: #38001 (https://...) - Repo-B: pushed (no PR) - STOP
If hub mode is not active: continue with normal flow below.
Persona (optional)
If .ai/me.md exists, read it. Use it to shape the PR description text. PR format constraints (summary + changes + test plan) always apply. If .ai/me.md doesn't exist, use defaults.
1. Locate the Spec Directory
SPEC_DIR=$(bash .ai/lib/dx-common.sh find-spec-dir $ARGUMENTS)
Read implement.md from $SPEC_DIR.
2. Verify All Steps Done
Parse implement.md and check that ALL steps have **Status:** done.
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.
- yesterday Changed · +4 lines · +7 tokens per session 49eb5451800e
- 2d ago Changed · -1 lines · +3 tokens per session babb026a2835
- 19d ago Changed ec0e143fbb79
- 1mo ago Changed c083b74cb012
- 1mo ago First seen · 193 lines · 51 tokens per session scan A 9a0e1f1dd086
dx-pr is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 2,014 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.