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-bug-all)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-bug-all"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-bug-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.00059 | $0.06458 |
| Opus 5 | $0.00030 | $0.03229 |
| Sonnet 5 | $0.00012 | $0.01292 |
| Haiku 4.5 | $0.00006 | $0.00646 |
Grade A, and why
dx-bug-all 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 7d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a coordinator for the bug pipeline. You delegate each step via the Skill tool — you never implement a fix yourself. You run in one of two modes, decided once up front:
- Local / interactive (
DX_PIPELINE_MODEunset) — the original hands-on flow: parse the id, optional hub dispatch, run triage → verify → fix withTaskListprogress and a retry-once on failure. This mode is unchanged from before recovery existed. - Pipeline / autonomous (
DX_PIPELINE_MODE=true) — the same three steps wrapped in resumable recovery: the per-ticketbugfix/<id>-*branch is a durable state store, every step checkpointsresume-state.json, a blocked/crashed run resumes when a human replies the trigger token, and the ticket never goes silent.
PIPELINE_MODE="${DX_PIPELINE_MODE:-}" # "true" → autonomous; else local
If PIPELINE_MODE is true, follow Pipeline mode below and ignore the Local-mode section. Otherwise follow Local mode.
Local mode (interactive — unchanged)
Progress Tracking
Before creating tasks, use TaskList to check for existing tasks from a previous run. If stale tasks exist, cancel them so the list is clean. Then create one task per item with TaskCreate: (1) Triage bug, (2) Verify reproduction, (3) Fix bug. Mark each in_progress when starting and completed when done.
Local flow
digraph bug_all_local {
"Parse argument" [shape=box];
"Hub dispatch?" [shape=diamond];
"Hub dispatch" [shape=box];
"Dispatch triage" [shape=box];
"Triage succeeded?" [shape=diamond];
"Dispatch verify" [shape=box];
"Dispatch fix" [shape=box];
"Fix succeeded?" [shape=diamond];
"Final summary + log run" [shape=doublecircle];
"Retry triage" [shape=box];
"Report FAIL (triage)" [shape=doublecircle];
"Retry fix" [shape=box];
"Report FAIL (fix)" [shape=doublecircle];
"Parse argument" -> "Hub dispatch?";
"Hub dispatch?" -> "Hub dispatch" [label="hub mode active"];
"Hub dispatch?" -> "Dispatch triage" [label="not hub mode"];
"Dispatch triage" -> "Triage succeeded?";
"Triage succeeded?" -> "Dispatch verify" [label="success"];
"Triage succeeded?" -> "Retry triage" [label="FAIL"];
"Retry triage" -> "Dispatch verify" [label="success"];
"Retry triage" -> "Report FAIL (triage)" [label="FAIL"];
"Dispatch verify" -> "Dispatch fix" [label="success | blocked | FAIL (warn + continue)"];
"Dispatch fix" -> "Fix succeeded?";
"Fix succeeded?" -> "Final summary + log run" [label="success"];
"Fix succeeded?" -> "Retry fix" [label="FAIL"];
"Retry fix" -> "Final summary + log run" [label="success"];
"Retry fix" -> "Report FAIL (fix)" [label="FAIL"];
}
What ships with it
7 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.
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.
- 7d ago First seen · 362 lines · 59 tokens per session scan A a236dcd42c6a
dx-bug-all is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 6,458 once invoked, about $0.0003 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
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
chrome-performance-optimizer
Autonomous multi-agent performance optimization loop for Chromium and V8. Supports profile-seeded mode (analyzing Speedometer 3 / JetStream profiles via pprof or Sagacity MCP) and pattern-driven discovery mode (fan-out exploration of Blink and V8 macro-patterns grounded in historical wins and past rejected CLs).…
nullaway
Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.