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-step-all)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-step-all"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-step-all/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-step-all"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-step-all.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 26 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Rogue Agent · line 48 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00047 | $0.05709 |
| Opus 5.5 | $0.00019 | $0.02284 |
| Sonnet 5.5 | $0.00009 | $0.01142 |
| Haiku 4.5 | $0.00005 | $0.00571 |
Grade A, and why
dx-step-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 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 — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a coordinator. You run the step pipeline for each step in implement.md, delegating to skills via the Skill tool.
Progress visibility
You run in a forked context. Before emitting any chat output, determine whether you were invoked by the orchestrator (dx-agent-all) or standalone — see plugins/dx-core/shared/orchestration-check.md:
ORCHESTRATED=0
FLAG=".ai/run-context/orchestrating.flag"
if [ -f "$FLAG" ]; then
AGE=$(( $(date +%s) - $(date -r "$FLAG" +%s) ))
[ "$AGE" -lt 7200 ] && ORCHESTRATED=1
fi
- If
$ORCHESTRATED == 1(orchestrator path): write all canonical artifacts to$SPEC_DIR/<file>.md(already documented below) and emit ONLY the## Returnblock to chat. - If
$ORCHESTRATED == 0(standalone path): write the same canonical artifacts AND emit the human-friendly summary marked<!-- standalone-only -->below, followed by the## Returnblock at the very end.
Per-phase / per-step progress lines during the run are allowed in both paths.
You run forked, so nothing inside this skill is visible to the orchestrator (dx-agent-all) — the progress file is the only channel. You MUST update $SPEC_DIR/dev-all-progress.md after each step transition:
- Mark step in_progress at the start of execution
- Mark step done | failed | healing immediately on transition
- Update within the same logical action — never batch updates
The orchestrator reads this file after this skill returns and prints a one-line status summary to the user. Skill invocations are blocking — the orchestrator does not poll mid-execution. If you skip an update, the user sees stale progress when they ask for a recap.
Write it with the shared script — it creates the file on first call and updates a row in place on later calls:
DX_PROGRESS_FILE="dev-all-progress.md" DX_PROGRESS_TITLE="Pipeline Progress" \
bash "$CLAUDE_PLUGIN_ROOT/shared/update-progress.sh" "$SPEC_DIR" "1: <title>" "in_progress"
Format — one row per step:
| Step | Status | Note |
|---|---|---|
| 1: | done | committed 4bf6fe5 |
| 2: | in_progress | — |
| 3: | — | — |
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 Changed · -1 lines · -4 tokens per session bd4209044123
- 24d ago Changed · +24 lines c7612a2d952f
- 1mo ago Changed · +9 lines f24a35527116
- 1mo ago First seen · 470 lines · 51 tokens per session scan A 8eee5f320f83
dx-step-all is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 5,709 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.