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 agentmods add skills/easingthemes/dx-aem-flow/auto-testnpx skills add easingthemes/dx-aem-flow --skill auto-testgit 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/auto-test)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/auto-test"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/auto-test.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.01761 |
| Opus 5 | $0.00026 | $0.00881 |
| Sonnet 5 | $0.00010 | $0.00352 |
| Haiku 4.5 | $0.00005 | $0.00176 |
Grade A, and why
auto-test 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 4d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You run an AI automation agent locally against real ADO data. With --dryRun, results are logged but nothing is posted to ADO or committed. Without --dryRun, the agent runs fully (posts comments, applies fixes).
0. Prerequisites
Check required env vars are set (in shell or .claude/settings.local.json):
ANTHROPIC_API_KEY- ADO MCP authenticated (browser OAuth) or
ADO_MCP_AUTH_TOKENset
1. Parse Arguments
From the user's command:
- Agent:
dor,dod,dod-fix,pr-review,pr-answer,bugfix,qa,devagent,docagent, orestimation - Target ID: work item ID (dor) or PR ID (pr-review, pr-answer)
- Repo name (pr-review, pr-answer)
--dryRunflag: defaulttruefor safety
If no arguments: Read .ai/automation/infra.json to get automationProfile and the list of enabled agents (those without "disabled": true). Then prompt with only the enabled agents:
Which agent to test?
Only show agents that are enabled for this profile:
- consumer (or legacy
pr-only/pr-delegation): PR Review, PR Answer, DevAgent, BugFix, DoD Fix - full-hub: all agents
Full agent list (filter to enabled):
- DoR — needs work item ID
- DoD — needs work item ID
- DoD Fix — needs work item ID
- PR Review — needs PR ID + repo name
- PR Answer — needs PR ID + repo name
- BugFix — needs Bug work item ID
- QA — needs work item ID
- DevAgent — needs work item ID (User Story)
- DOCAgent — needs work item ID (User Story)
- Estimation — needs work item ID
If the user requests an agent that is disabled for this profile, report: ⚠ <agent> is not enabled for the <profile> profile. To enable it, re-run /auto-init.
Target ID? (work item ID or PR ID)
Dry run? (default: yes — log results without posting to ADO)
- Yes — dry run (recommended for first test)
- No — live run (posts real comments/applies fixes)
2. Run Agent
node .ai/automation/scripts/pipeline-agent.js "<skill-prompt>"
Map agent names to skill prompts:
| Agent | Skill Prompt |
|---|---|
| dor | /dx-req-dod <id> |
| dod | /dx-req-dod <id> |
| dod-fix | /dx-req-dod <id> |
| pr-review | /dx-pr-review <pr-url> analyze only (dry run) or /dx-pr-review <pr-url> (live) |
| pr-answer | /dx-pr-answer <pr-url> |
| bugfix | /dx-bug-all <id> |
| devagent | /dx-agent-all <id> |
| docagent | /dx-doc-gen <id> |
| estimation | /dx-estimate <id> |
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.
- 4d ago First seen · 145 lines · 52 tokens per session scan A 6d39e43ed64d
auto-test is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 1,761 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…