Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add easingthemes/dx-aem-flow --skill dx-step-buildgit clone --depth 1 https://github.com/easingthemes/dx-aem-flowWrote 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-build)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-step-build"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-step-build/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-build"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-step-build.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.00035 | $0.01842 |
| Opus 5.5 | $0.00014 | $0.00737 |
| Sonnet 5.5 | $0.00007 | $0.00368 |
| Haiku 4.5 | $0.00003 | $0.00184 |
Grade A, and why
dx-step-build 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You build and deploy the project, diagnose any failures, fix them, and repeat until the build passes.
Flow
digraph step_build {
"Discover build command" [shape=box];
"Run build" [shape=box];
"Build passed?" [shape=diamond];
"Attempt < 6?" [shape=diamond];
"Find error + read file" [shape=box];
"Diagnose + fix" [shape=box];
"Re-run build" [shape=box];
"Report PASS" [shape=doublecircle];
"Report FAIL (6 attempts exhausted)" [shape=doublecircle];
"Discover build command" -> "Run build";
"Run build" -> "Build passed?";
"Build passed?" -> "Report PASS" [label="yes"];
"Build passed?" -> "Attempt < 6?" [label="no"];
"Attempt < 6?" -> "Find error + read file" [label="yes"];
"Attempt < 6?" -> "Report FAIL (6 attempts exhausted)" [label="no"];
"Find error + read file" -> "Diagnose + fix";
"Diagnose + fix" -> "Re-run build";
"Re-run build" -> "Build passed?";
}
Node Details
Discover build command
If the user provided an argument, use that as the build command.
Otherwise, read from .ai/config.yaml. Choose the right command based on context:
| Config key | When to use | Example |
|---|---|---|
build.deploy |
Quick rebuild during fix loops, FE verification, iterative development | mvn clean install -PautoInstallPackage -DskipTests |
build.command |
Final pipeline build, when tests must run | mvn clean install -PautoInstallPackage |
Default: Use build.deploy if available (faster — skips tests). Fall back to build.command if build.deploy is not configured.
Exception: When called from the main pipeline build phase (dx-agent-all Phase 5), use build.command to include tests. The caller can override by passing an explicit argument.
If neither is found, read CLAUDE.md and README.md to find the project's build-and-deploy command. Look for a command that both builds and deploys to a local dev environment.
Print: Using build command: \``
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 · +5 tokens per session a9ab53393ada
- 2d ago Changed · -1 lines · -5 tokens per session 1b63e0e32d95
- 1mo ago First seen · 202 lines · 35 tokens per session scan A 6200847059e5
dx-step-build 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 1,842 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…