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 instructions/easingthemes/dx-aem-flow/agents-mdgit 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/instructions/easingthemes/dx-aem-flow/agents-md)<a href="https://agentmods.dev/instructions/easingthemes/dx-aem-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/easingthemes/dx-aem-flow/agents-md.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.00888 | $0.00888 |
| Opus 5 | $0.00444 | $0.00444 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
dx-aem-flow AGENTS.md 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cross-tool agent instructions for dx-aem-flow — AI-assisted Azure DevOps development workflows.
This file is the cross-platform equivalent of
CLAUDE.md. Tools that read AGENTS.md include Codex, Copilot, Cursor, Windsurf, Zed, Jules, Gemini CLI, and others. Claude Code readsCLAUDE.md(which contains the full contributor guide); this file provides the essential subset for all other agents.
What This Is
Four installable plugins for AI-assisted development workflows. Pure Markdown (skills, agents, rules, templates) with shell helper scripts. No build system.
| Plugin | Directory | Purpose | Skill prefix |
|---|---|---|---|
| dx-core | plugins/dx-core/ |
Platform-agnostic ADO/Jira workflow: requirements, planning, execution, review, PR | dx-* |
| dx-hub | plugins/dx-hub/ |
Multi-repo orchestration | dx-hub-* |
| dx-aem | plugins/dx-aem/ |
AEM-specific verification, QA, demo capture | aem-* |
| dx-automation | plugins/dx-automation/ |
Autonomous AI agents running as ADO pipelines | auto-* |
Plugin Structure
Each plugin follows this layout:
plugin/
├── .claude-plugin/plugin.json # Plugin manifest
├── .mcp.json # MCP server config
├── agents/ # Agent definitions (*.md with YAML frontmatter)
├── skills/ # Skill directories (*/SKILL.md)
├── rules/ # Default prompt templates
├── hooks/ # Lifecycle hooks
├── data/ # Seed files copied to project by init
├── shared/ # Reference files read by skills at runtime
└── templates/ # Init-time file templates
Key Conventions
Config-Driven — Never Hardcode
All project-specific values live in .ai/config.yaml. Skills read config at runtime. Never hardcode build commands, branch names, URLs, or org names.
Spec Directory Convention
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.
- 3d ago First seen · 91 lines · 888 tokens per session scan A 94b274bd6565
dx-aem-flow AGENTS.md is an instructions file published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 888 tokens to every session, about $0.0044 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.