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-review-triagegit 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-triage)<a href="https://agentmods.dev/skills/dikamilo/dx-workflow/dx-review-triage"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-review-triage/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-triage"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-review-triage.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.00020 | $0.00917 |
| Opus 5.5 | $0.00008 | $0.00367 |
| Sonnet 5.5 | $0.00004 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
dx-review-triage 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-review-triage
Turn a review report's findings into decisions — and, when you say so, into edits. Every review (dx-review) only analyzes and reports; this is the one place that acts on a finding, one finding at a time, only on your confirmation.
Guard. Resolve <container-id> under context/changes/ or context/efforts/. If it resolves under context/archive/ instead, refuse: archived work is done. If reviews/ is missing or holds no report, point at /dx-review <policy-id> <container-id>.
1 — Resolve which report
A report lives at reviews/<policy-id>.md, one per Policy, always the current review because a re-run overwrites it.
- A policy ID given →
reviews/<policy-id>.md. If the file is missing, name it and list the reports that exist. - No policy ID → exactly one report → use it; several → ask which, since each can carry open findings at once.
A legacy reviews/impl-review.md or reviews/plan-review.md is never read and doesn't count as a report: if one is all there is, say it's superseded and point at /dx-review implementation <container-id> or /dx-review plan <container-id> respectively.
Load first
The report's schema — the finding/Resolution format, the resume rule, the never-commit rule — is context/config/templates/review-report.md (missing → /dx-init).
2 — Walk findings in order
Resume at the first finding with Resolution: PENDING, document order. Load what that finding's Location names — a plan section → plan.md; a file:line → that file plus enough surrounding code or git log to judge the fix — and nothing for findings you skip. Show its title, location, detail, and suggested fix, then ask:
- Fix now — apply the suggested fix (or a variant you propose); show the before/after edit first, apply on confirmation.
- Fix differently — ask what they'd prefer instead, apply that.
- Skip — leave it for now, move on.
- Accept risk — leave it, record the one-line reason.
- Record as lesson — hand the finding's title and detail to
/dx-lesson's entry shape and tell the user to confirm there. Never append tofoundation/lessons.mdyourself — that file has exactly one writer.
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 · -4 tokens per session 40310efbcf5c
- 1mo ago Changed bfce313de1c4
- 2mo ago First seen · 57 lines · 24 tokens per session scan A 03d617f7fe04
dx-review-triage is a skill published in the GitHub repository dikamilo/dx-workflow (8 stars, last pushed 23d ago), licensed MIT. It adds 20 tokens to every session and 917 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
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…