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 skills add easingthemes/dx-aem-flow --skill dx-hub-statusgit 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/dx-hub-status)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-hub-status"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-hub-status/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-status"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-hub-status.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.00032 | $0.01207 |
| Opus 5.5 | $0.00013 | $0.00483 |
| Sonnet 5.5 | $0.00006 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade C, and why
dx-hub-status scanned grade C 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- If age exceeds TTL AND no repo is `running`, delete the directory with one `rm -rf state/<ticket-id>` per directory, the ticket id written out literally — never `state` or `state/` itself, no shell variable, loop or `$ 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 display the status of hub dispatches across all configured repos.
Before anything else, read .ai/config.yaml. If hub.enabled is not true, STOP with:
Hub mode is not enabled. Run `/dx-hub-init` first.
1. Parse Arguments
- No argument → show all active dispatches (summary table)
<ticket-id>→ detailed view for that one ticket--clean→ remove state entries older thanhub.state-ttl, report count
Read from config:
hub.state-ttl— retention period for clean mode (default:7d)repos[]— list of repos with paths (for reading spec dirs in detailed view)
2. Load Status Files
Glob state/*/status.json to find all dispatch state files.
If no files found, print: No active dispatches found. Run /dx-hub-dispatch to start one. and STOP.
3. Display
All dispatches (no argument)
Print a summary table:
Hub Dispatch Status
───────────────────────────────────────────────────
┌──────────┬─────────────────────────┬──────────────┬──────────┐
│ Ticket │ Title │ Repo │ Status │
├──────────┼─────────────────────────┼──────────────┼──────────┤
│ 2471234 │ Add user profile page │ repo-fe │ done │
│ │ │ repo-be │ running │
│ 2471189 │ Fix auth timeout │ repo-be │ blocked │
└──────────┴─────────────────────────┴──────────────┴──────────┘
Legend: done ✓ running ⟳ blocked ⚠ failed ✗
For multi-repo dispatches, show ticket and title only on the first row.
Single ticket (<ticket-id> argument)
Find state/<ticket-id>/status.json. If not found, print: No dispatch found for ticket <ticket-id>. and STOP.
Read the status file and print:
## Dispatch: <ticket-id> — <title>
**Type:** <type>
**Skill:** <skill>
**Started:** <started timestamp>
### Repo Status
| Repo | Status |
|------|--------|
| <repo-a> | done |
| <repo-b> | running |
If any repo is blocked, add:
⚠ <repo-name> is blocked — switch to its terminal to investigate.
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 · -15 tokens per session 48f95b873b6e
- 1mo ago First seen · 146 lines · 47 tokens per session scan C 662015f8ea45
dx-hub-status is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 1,207 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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…