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-reviewgit 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-review)<a href="https://agentmods.dev/skills/dikamilo/dx-workflow/dx-review"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-review/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-review"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-review.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.01876 |
| Opus 5.5 | $0.00011 | $0.00750 |
| Sonnet 5.5 | $0.00005 | $0.00375 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
dx-review 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-review
Run one review, on a container or as an Explore run over the repo or folders. The Policy at context/config/review-policies/<policy-id>.md holds the criteria: its preconditions, what to load, the dimensions and extra checks, what a pass sets, and the next steps. This skill holds the mechanism and applies the Policy as written. Report only: never edit what you're reviewing; an Explore run writes only a promoted Change's change.md and research/ (nothing, under promote: off). Fixes belong to /dx-review-triage.
Guard.
- Policy. If
context/config/review-policies/is missing, point at/dx-init. A policy ID is the name of any.mdthere. If the ID is unknown, name it, list the available IDs, and note that re-running/dx-initseeds any built-in Policy the project is missing. If the Policy'stargetsis missing or isn't one ofcontainer | explore | both, refuse and name the field. - Arguments. The first is the policy ID. The rest resolve positionally: a container ID (
context/changes/<id>/orcontext/efforts/<id>/), else the leading tokens that are existing repo paths, and the first token that is neither starts the custom instructions. A container ID undercontext/archive/is refused: archived work is done. A container plus a path is refused as ambiguous. No container and no paths is an Explore run over the whole repo. - Target.
containerrefuses an Explore run,explorerefuses a container run,bothaccepts either; every refusal names the Policy and the targets it accepts. An Explore run on a Policy with no## Candidatesis refused, naming the section. - Input acquisition. An Explore run with no container and no paths asks what to review before reading anything. Print the interpreted scope before the fan-out.
- Preconditions. Check every precondition the Policy lists. A failing precondition refuses the run with the next command it names.
1 — Load
Load what the Policy's ## Load names, with each conditional load gated on its trigger. Also load context/config/templates/review-report.md (missing → /dx-init) and foundation/glossary.md. The glossary is a one-line habit: judge naming against the project's terms, and if the work's naming clashes with it or settles a term, invoke dx-domain. Custom instructions narrow or steer the run, but they never skip a precondition, and a dimension they leave unchecked is reported N/A, not PASS.
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 First seen · 64 lines · 27 tokens per session scan A b9d898d771f4
dx-review 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 1,876 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-10-08.
Other skills, from other repositories
agent-watchdog
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, independently investigate the same…
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
graphify-dotnet
Use graphify-dotnet to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
prism
Split one artifact — a claim, plan, or file — across 2 to 5 independent lenses, one per genuinely distinct failure mode (correctness, security, readability, cost, adversarial-user), and return their convergence: where they agree, where they disagree, and the single next question that resolves the disagreement. Use…