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-init)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-init"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-init/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-init"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-init.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.00043 | $0.12047 |
| Opus 5.5 | $0.00017 | $0.04819 |
| Sonnet 5.5 | $0.00009 | $0.02409 |
| Haiku 4.5 | $0.00004 | $0.01205 |
Grade A, and why
dx-init 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 — 949 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You configure the dx workflow for the current project by detecting the environment, asking the user a few key questions, and generating .ai/config.yaml.
Re-run Validation Protocol
CRITICAL: When dx-init is re-run on a project that is already set up, EVERY step MUST execute. NEVER stop early. If the user chooses "Keep as-is" for config, skip to step 5 and continue through ALL remaining steps (5→6→7→8→9→10→11). Each step validates existing files against plugin data:
| File Category | Re-run Behavior |
|---|---|
| Config (config.yaml) | Ask: keep / modify / regenerate |
| Utility scripts (audit.sh, stop-guard.sh) | Compare against plugin version → update silently if changed |
| Template-generated (README.md, agent.index.md) | Compare against latest template → update if template is newer |
| Docs (.ai/docs/) | Removed — plugin docs are public at https://easingthemes.github.io/dx-aem-flow/ |
| Rule files (.ai/rules/, .claude/rules/) | Compare against template → if only template changed: update. If user customized: report diff, ask user |
| User-owned (me.md) | Never touch — always skip |
| MCP config (.mcp.json) | Validate configured values match current project config |
The scaffold script handles utility and rule validation automatically. Template-generated files are validated inline by each step.
1. Check Existing Config
Check if .ai/config.yaml exists at the project root (use Glob tool).
- If it exists: Read and display the current config, then ask: "Config already exists. (A) Keep as-is, (B) Modify, or (C) Start fresh?"
- If A: Say "Config kept. Validating all project files..." — then check if
.ai/config.yamlhas apreferences:section with bothauto-commitandauto-prkeys. If either key is missing: run Step 4 (Preferences) to ask the user, then append thepreferences:section to the existing config.yaml. After that, CONTINUE to step 5 to validate all generated files, scripts, rules, and templates. DO NOT stop or exit. The re-run must validate everything. - If B: Load existing values as defaults, go to step 2
- If C: Go to step 2 with no defaults
- If A: Say "Config kept. Validating all project files..." — then check if
- If it doesn't exist: Say "No dx config found. Let's set up your project." Go to step 2.
What ships with it
3 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.
- yesterday Changed · +3 lines 8f43f40b4697
- 2d ago Changed · +9 lines 3d3c7943996b
- 3d ago Changed · -10 lines 7001d0b6bb7c
- 19d ago Changed ffa897356050
- 29d ago Changed · +5 lines 5f09bb82e423
- 1mo ago Changed 338b848a0961
- 1mo ago First seen · 942 lines · 43 tokens per session scan A 695b4e9741a8
dx-init is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 12,047 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
gsd-ns-manage
config workspace | workstreams thread update ship inbox.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
cs-escalation-brief
Redacta un informe de escalada estructurado para una cuenta de cliente en riesgo. Úsalo cuando una cuenta haya escalado, cuando un cliente amenace con cancelar, cuando un problema de cliente P1 requiera atención ejecutiva, o cuando prepares un plan de retención interno. Produce un informe de escalada preciso con…