Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/easingthemes/dx-aem-flownpx agentmods add skills/easingthemes/dx-aem-flow/dx-syncWrote 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-sync)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-sync"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-sync/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-sync"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-sync.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.00039 | $0.00976 |
| Opus 5.5 | $0.00016 | $0.00390 |
| Sonnet 5.5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
dx-sync 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You sync plugin updates to consumer AEM repos using the sync-consumers.sh script. Any consumer repo can run this skill — there is no hub. Repos are listed in .ai/config.yaml under repos:.
1. Locate Sync Script
The sync script lives in this skill's scripts directory:
SYNC_SCRIPT="${CLAUDE_SKILL_DIR}/scripts/sync-consumers.sh"
If it doesn't exist, try the repo root fallback:
SYNC_SCRIPT="$(git rev-parse --show-toplevel)/internal/sync-consumers.sh"
If neither exists, STOP: "sync-consumers.sh not found."
2. Show Consumer Repo Table
Read repos: from .ai/config.yaml. Present the available repos and their capabilities:
| Repo | Path | Base Branch | Work Branch | FE | BE |
|------|------|-------------|-------------|:--:|:--:|
| brand-a | ../Brand-A-Project | development | feature/ai-sync | Yes | No |
| backend | ../AEM-Backend | develop | feature/ai-sync | Yes | Yes |
| brand-b | ../Brand-B-Project | development | feature/ai-sync | Yes | No |
All repos come from the
repos:section in.ai/config.yaml. The current repo is excluded (you don't sync to yourself).
3. Parse Arguments
From $ARGUMENTS, extract:
- Flags:
--dry-run,--parallel,--no-git,--no-pr - Repos: Repo names from
.ai/config.yamlrepos:section - If no repos specified, defaults to all configured repos
If no arguments at all, ask: "Sync all repos? Or specify which ones (e.g., brand-a backend). Add --dry-run to preview."
4. Run Sync
bash "$SYNC_SCRIPT" $ARGUMENTS
The script handles:
- Merge
origin/<base-branch>into work branch - Copy utility scripts to
.ai/lib/ - Copy output templates to
.ai/templates/ - Generate Copilot agents (with dual tool names for Copilot CLI + VS Code Chat)
- Config migration (runs versioned migrations on the consumer's
.ai/config.yaml; updatesdx.versionto match the plugin version) - Sync Claude rules (
.claude/rules/) - Sync AI rules (
.ai/rules/) - Sync instructions (
.github/instructions/) - Sync VS Code MCP config (
.vscode/mcp.json— mirrors ADO/Atlassian from root.mcp.json) - Sync VS Code Chat settings (
.vscode/settings.json—chat.instructionsFilesLocations,chat.agentSkillsLocations) - Cleanup (remove rules not applicable to repo capabilities)
- Commit and push
- Create/update PR
What ships with it
2 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.
- 2d ago Changed · +1 lines c1f042778ef3
- 1mo ago First seen · 93 lines · 39 tokens per session scan A 7edc59aa7e55
dx-sync is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 976 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.