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-req-dod)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-req-dod"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-req-dod/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-req-dod"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-req-dod.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.04120 |
| Opus 5.5 | $0.00026 | $0.01648 |
| Sonnet 5.5 | $0.00013 | $0.00824 |
| Haiku 4.5 | $0.00007 | $0.00412 |
Grade A, and why
dx-req-dod 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Defaults
Read shared/provider-config.md for provider detection and tool mapping.
Read .ai/config.yaml:
tracker.provider(orscm.providerfor backward compat) —ado(default) orjira
If provider = ado:
- Organization:
scm.org - Project:
scm.project
If provider = jira:
- Jira URL:
jira.url - Project Key:
jira.project-key - Note: ADO state "Resolved" varies by Jira workflow — use
fields.status.nameto check the equivalent status.
You check whether a work item meets the Definition of Done. You fetch the DoD checklist from the wiki, check ADO/Jira state and codebase via MCP, and produce dod.md — a structured pass/fail report.
This validates the actual deliverables (code, tests, PR, build) — not agent workflow artifacts. Works the same whether the story was implemented manually or via the AI workflow.
Use ultrathink for this skill — cross-referencing multiple sources (ADO/Jira state, codebase, PR status) requires systematic verification.
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 phase transition:
DX_PROGRESS_FILE="dod-progress.md" DX_PROGRESS_TITLE="/dx-req-dod Progress" \
bash "$CLAUDE_PLUGIN_ROOT/shared/update-progress.sh" "$SPEC_DIR" "<phase>" "<status>"
Status values: pending · in_progress · done · failed · skipped · blocked. One row per phase, updated in place.
If TaskCreate is in this session's tool list, also mirror the same phases 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 phase transition on a task tool being present.
- DoD Check (gather evidence, evaluate criteria)
- Auto-Fix Gaps (if failures found)
- Post to ADO/Jira
1. Resolve Work Item
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 · +36 tokens per session 245b6d50de9a
- 19d ago Changed · +3 lines a4ff29100e0e
- 1mo ago Changed · +9 lines 6f67bc08e003
- 1mo ago First seen · 392 lines · 30 tokens per session scan A 8171dc74c970
dx-req-dod is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 4,120 once invoked, about $0.0003 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
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.