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-hub-initWrote 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-hub-init)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-hub-init"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-hub-init/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-hub-init"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-hub-init.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.00056 | $0.04310 |
| Opus 5.5 | $0.00022 | $0.01724 |
| Sonnet 5.5 | $0.00011 | $0.00862 |
| Haiku 4.5 | $0.00006 | $0.00431 |
Grade B, and why
dx-hub-init scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Pick the first selected repo. Read `<repo-path>/.claude/settings.json`. Extract: How it starts
The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You set up a .hub/ directory that orchestrates work across multiple repos via dx-core hub mode.
Flow
digraph hub_init {
"Validate CLI" [shape=box];
"CLI compatible?" [shape=diamond];
"STOP: CLI incompatible" [shape=doublecircle];
"Determine hub path" [shape=box];
"Hub already exists?" [shape=diamond];
"Confirm reinit" [shape=diamond];
"STOP: User cancelled" [shape=doublecircle];
"Discover repos" [shape=box];
"Present repos" [shape=box];
"User selects repos" [shape=diamond];
"Build config" [shape=box];
"Create hub structure" [shape=box];
"Configure Claude Code settings" [shape=box];
"Generate CLAUDE.md" [shape=box];
"Offer workspace file" [shape=diamond];
"Create .code-workspace" [shape=box];
"Summary" [shape=doublecircle];
"Validate CLI" -> "CLI compatible?";
"CLI compatible?" -> "Determine hub path" [label="yes"];
"CLI compatible?" -> "STOP: CLI incompatible" [label="no"];
"Determine hub path" -> "Hub already exists?";
"Hub already exists?" -> "Confirm reinit" [label="yes"];
"Hub already exists?" -> "Discover repos" [label="no"];
"Confirm reinit" -> "Discover repos" [label="yes, reinit"];
"Confirm reinit" -> "STOP: User cancelled" [label="no"];
"Discover repos" -> "Present repos";
"Present repos" -> "User selects repos";
"User selects repos" -> "Build config" [label="confirmed"];
"User selects repos" -> "STOP: User cancelled" [label="none selected"];
"Build config" -> "Create hub structure";
"Create hub structure" -> "Configure Claude Code settings";
"Configure Claude Code settings" -> "Generate CLAUDE.md";
"Generate CLAUDE.md" -> "Offer workspace file";
"Offer workspace file" -> "Create .code-workspace" [label="yes"];
"Offer workspace file" -> "Summary" [label="no"];
"Create .code-workspace" -> "Summary";
}
Node Details
Validate CLI
Run:
claude --version
claude -p --help 2>&1 | grep -q 'output-format'
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 1c6be3fad598
- 3d ago Changed · -3 lines 1befde89a232
- 19d ago Changed 67136fd996e6
- 1mo ago First seen · 478 lines · 56 tokens per session scan B a6cb974a7dad
dx-hub-init is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 4,310 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…