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)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-step"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-step/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"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-step.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Rogue Agent · line 14 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.00035 | $0.06018 |
| Opus 5.5 | $0.00014 | $0.02407 |
| Sonnet 5.5 | $0.00007 | $0.01204 |
| Haiku 4.5 | $0.00003 | $0.00602 |
Grade A, and why
dx-step 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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You execute the next pending step from implement.md — implement the changes, verify compilation, run tests, review against plan and conventions, commit, and mark the step done.
You run forked (context: fork): coordinators (dx-step-all, dx-bug-fix) call you once per step and read only your final ## Return block. Before printing anything user-facing, check whether a step loop is driving you (see plugins/dx-core/shared/orchestration-check.md § Step-loop marker):
IN_STEP_LOOP=0
LOOP_FLAG=".ai/run-context/step-loop.flag"
if [ -f "$LOOP_FLAG" ]; then
AGE=$(( $(date +%s) - $(date -r "$LOOP_FLAG" +%s) ))
[ "$AGE" -lt 7200 ] && IN_STEP_LOOP=1
fi
You are the worker for one step. Never invoke Skill(dx-step) or /dx-step-all yourself. The loop belongs to the coordinator.
$IN_STEP_LOOP == 1 only suppresses the "run X next" hints addressed to a human — it never changes what the step does.
Progress Tracking
Follow .ai/rules/task-progress.md (plugin default: rules/task-progress.md). The progress file is the source of truth — write it at every step transition:
DX_PROGRESS_FILE="dev-all-progress.md" DX_PROGRESS_TITLE="Pipeline Progress" \
bash "$CLAUDE_PLUGIN_ROOT/shared/update-progress.sh" "$SPEC_DIR" "<n>: <title>" "<status>"
The row key is <n>: <title> — the step number and title exactly as they appear
in implement.md. dx-step-all invokes this skill once per step and writes the
same file with the same key and the same DX_PROGRESS_TITLE, so a step must
produce one row however it was started, and dx-agent-all counts it (its
counters anchor on ^\| [0-9]+:). Never key a row on a free-form label.
Status values: pending · in_progress · done · failed · skipped · blocked. One row per step, updated in place.
If TaskCreate is in this session's tool list, also mirror the same steps into tasks so the user gets a live checklist — TaskList first to cancel stale tasks from an interrupted run. If it is absent (the default on Opus 4.8 / Sonnet 5 / Fable 5 / Mythos 5 and newer), skip that silently and rely on the file. Never block a step transition on a task tool being present.
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 · -19 tokens per session ef7b7a00e1ae
- 24d ago Changed · +46 lines e229ad2e6fb0
- 1mo ago Changed · +15 lines 6b162c32e158
- 1mo ago First seen · 437 lines · 54 tokens per session scan A d38a079cf95c
dx-step is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 6,018 once invoked, about $0.0001 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.