agentmods.dev

dx-agent-re

dx-agent-re is a skill for Claude Code from easingthemes/dx-aem-flow. It costs 64 tokens per session (2,663 once invoked), scanned A, original, MIT.

A requirements-analysis workflow that reads a work item from Azure DevOps or Jira and turns it into a clear specification with smaller development tasks.

In plain words
What is it for?
Use it to analyze a user story, review related project information and code, create a requirements document, and prepare child tasks for a developer.
Why use it?
It removes the need to manually gather story details and decide how to break the work down. It can also add a summary to the work item, with approval.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Part of the dx-core plugin — 49 skills, 7 agents shipped together

not rated 6repo 7d ago A scan 64 tokens original MIT

Good fit Use it to analyze a user story, review related project information and code, create a requirements document, and prepare child tasks for a developer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/easingthemes/dx-aem-flow/dx-agent-re
View source ↗ easingthemes/dx-aem-flow
Install

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.

Any agent
npx skills add easingthemes/dx-aem-flow --skill dx-agent-re
Clone the repo
git clone --depth 1 https://github.com/easingthemes/dx-aem-flow

Made for: Claude Code.

Or install dx-core, the plugin that ships this one along with the rest of its 49 skills, 7 agents.

Wrote 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.

agentmods badge for dx-agent-re

README.md
[![agentmods](https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-agent-re/github.svg)](https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-agent-re)
Your own site
<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-agent-re"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-agent-re/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.

agentmods 80×15 button for dx-agent-re

Your own site · 80×15
<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-agent-re"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-agent-re.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,663 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.02663
Opus 5 $0.00032 $0.01332
Sonnet 5 $0.00013 $0.00533
Haiku 4.5 $0.00006 $0.00266

Measured 9d ago against content hash 08858255eba9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

dx-agent-re 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 9d 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.

plugins/dx-core/skills/dx-agent-re/SKILL.md · 283 lines

How it starts

The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the RE Agent (Requirements Engineering). You analyze an ADO User Story and produce a structured requirements spec with task breakdown for the Dev Agent.

Role Constraints

Read .ai/automation/agents/roles/re-agent.yaml for your role definition. Key rules:

  • canModifyCode: false — you NEVER modify source code
  • capabilities: readWorkItem, readWiki, readCode, postComment, updateWorkItem, createChildWorkItems
  • adoActions: updateStory, createTasks
  • Human-in-the-loop: ask before posting comments or creating child work items

Defaults

Read shared/provider-config.md for provider detection and tool mapping. Read shared/ado-config.md for ADO-specific details.

Read .ai/config.yaml:

  • tracker.provider (or scm.provider for backward compat) — ado (default) or jira

If provider = ado:

  • Organization: scm.org
  • Project: scm.project

If provider = jira:

  • Jira URL: jira.url
  • Project Key: jira.project-key
  • Custom Fields: jira.custom-fields.*

Hub Mode Check

Read shared/hub-dispatch.md for hub detection logic.

If hub mode is active (hub.enabled: true AND cwd is .hub/):

  1. Read .ai/config.yaml → repos: list
  2. If a specific repo is needed (from ticket context or user hint), resolve to config entry
  3. If multiple repos might be involved, dispatch to each:
    • Build: cd <repo.path> && claude -p "/dx-agent-re <ticket-id>" --output-format json --allowedTools "Bash,Read,Edit,Write,Glob,Grep" --permission-mode bypassPermissions
    • Collect results per repo
  4. Write state files, print summary
  5. STOP — do not continue with local execution

If hub mode is not active: continue with normal flow below.

1. Parse Input

The argument is the ADO work item ID (e.g., 2435084).

If a URL like https://{org}.visualstudio.com/.../_workitems/edit/<id>, extract the numeric ID.

If no argument, ask the user.

2. Fetch User Story

mcp__ado__wit_get_work_item
  project: "<ADO project>"
  id: <work item ID>
  expand: "relations"

Read the full file on GitHub · 283 lines

Changes

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.

  1. 9d ago First seen · 283 lines · 64 tokens per session scan A 08858255eba9

Subscribe to this mod's changes

dx-agent-re is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 2,663 once invoked, about $0.0003 per session on Opus 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-08-31.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens