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 dikamilo/dx-workflow --skill dx-initgit clone --depth 1 https://github.com/dikamilo/dx-workflowWrote 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/dikamilo/dx-workflow/dx-init)<a href="https://agentmods.dev/skills/dikamilo/dx-workflow/dx-init"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-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/dikamilo/dx-workflow/dx-init"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-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.00027 | $0.00768 |
| Opus 5.5 | $0.00011 | $0.00307 |
| Sonnet 5.5 | $0.00005 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
dx-init 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 22d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-init
Set up the context/ tree the dx- workflow reads and writes. Idempotent by contract: create what's missing, never touch what exists. Re-running is safe.
Scaffold
Create (only if absent) under context/:
foundation/ glossary.md, lessons.md, research/
standards/ global/, frontend/, backend/, testing/
efforts/ changes/ archive/
config/ review-policies/, templates/
- Standards: decide first whether
context/standards/existed before this run.- Absent (fresh context): seed the three global standards by copying
${CLAUDE_SKILL_DIR}/assets/standards/global/*.mdintocontext/standards/global/. - Present: copy nothing — a project removes and replaces the shipped standards, and re-seeding resurrects what it deleted. List the shipped standards that aren't in
context/standards/global/and ask which, if any, to copy. Copy only the ones the user names; never overwrite an existing file.
- Absent (fresh context): seed the three global standards by copying
- Seed the review Policies and templates by copying
${CLAUDE_SKILL_DIR}/assets/config/intocontext/config/(review-policies/*.mdandtemplates/*.md), missing files only. They are user-owned from then on:/dx-reviewreads them, and a project may edit or add to them. standards/{frontend,backend,testing}/ship empty —dx-standards-discoverfills them per-project from the real codebase.foundation/glossary.mdandfoundation/lessons.mdget a one-line header each and nothing more (e.g.# Glossary — ubiquitous language for this project/# Lessons — accrued warnings and load-bearing decisions (append-only)). They stay empty;dx-domain-discoveranddx-lessonfill them.
Agent instructions file
Write to the project's root AGENTS.md when it exists and CLAUDE.md is absent or holds only a pointer to it (e.g. @AGENTS.md); otherwise write to CLAUDE.md, creating it if absent. Keep everything dx- owns inside one managed block, so later injections edit only that block and the rest of the file stays the user's:
What ships with it
9 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.
- assets/config/review-policies/implementation.md 2.7 KB
- assets/config/review-policies/plan.md 3.6 KB
- assets/config/review-policies/sessions.md 7.8 KB
- assets/config/review-policies/test-strategy.md 6.3 KB
- assets/config/templates/review-policy.md 4.9 KB
- assets/config/templates/review-report.md 2.9 KB
- assets/standards/global/coding-style.md 1.1 KB
- assets/standards/global/conventions.md 798 B
- assets/standards/global/minimal-implementation.md 1.0 KB
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.
- 22d ago Changed · +13 lines · +3 tokens per session e7c5b8c2bb89
- 2mo ago First seen · 41 lines · 24 tokens per session scan A c499f07b043d
dx-init is a skill published in the GitHub repository dikamilo/dx-workflow (8 stars, last pushed 23d ago), licensed MIT. It adds 27 tokens to every session and 768 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
factory-collect
Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.
factory-human-digest
Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.
factory
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.