Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add easingthemes/dx-aem-flow/plugin install dx-coreWrote 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-agent-all)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-agent-all"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-agent-all.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.00045 | $0.09101 |
| Opus 5 | $0.00023 | $0.04550 |
| Sonnet 5 | $0.00009 | $0.01820 |
| Haiku 4.5 | $0.00005 | $0.00910 |
Grade B, and why
dx-agent-all scanned grade B 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 8d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Check the plan-validate result. If FAIL, stop. If PASS (with or without warnings), continue to feature branch creation. How it starts
The opening of the file, as written. The whole thing — 738 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the top-level coordinator. You orchestrate the entire development pipeline from ADO story to pull request.
Argument
The argument is the ADO work item ID — a numeric value (e.g., 2435084).
If the user provides a full ADO URL, extract the numeric ID.
If no argument is provided, ask the user for the work item ID.
Run-State Management
Maintain run state in $SPEC_DIR/run-state.json:
{
"skill": "dx-agent-all",
"ticket": "<id>",
"started": "<ISO-8601>",
"last_phase_completed": 0,
"total_phases": 0
}
On invocation:
- Check for existing
$SPEC_DIR/run-state.json - If exists and fresh (<2 hours) → ask: "Previous run found at phase {last_phase_completed}/{total_phases}. Resume or start fresh?"
- If stale → start fresh, delete old state
- If not exists → create new
During execution: Update after each phase. On completion: Delete run-state.json.
Orchestration Flag
In addition to run-state.json, write a marker file .ai/run-context/orchestrating.flag at startup. Forked sub-skills check this file to determine whether they're running under the orchestrator (compact ## Return only) or standalone (verbose summary + ## Return).
On invocation, after run-state.json is created:
mkdir -p .ai/run-context
touch .ai/run-context/orchestrating.flag
After each phase transition (alongside run-state.json update):
touch .ai/run-context/orchestrating.flag
This refreshes the mtime so a long-running pipeline doesn't trip the 2h staleness check inside forked skills.
On any terminal state — Final Summary, STOP, validation failure, build/review failure routes:
rm -f .ai/run-context/orchestrating.flag
The flag's existence (and freshness) is the signal that forked sub-skills (dx-req, dx-plan, dx-plan-validate, dx-plan-resolve, dx-pr-commit, dx-step-all) read to suppress their human-friendly summary output. See plugins/dx-core/shared/orchestration-check.md.
What ships with it
1 file 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.
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.
- 8d ago First seen · 738 lines · 45 tokens per session scan B 001af178192b
dx-agent-all is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 9,101 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.