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-plan-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-plan-review)<a href="https://agentmods.dev/skills/dikamilo/dx-workflow/dx-plan-review"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-plan-review.svg" alt="Measured on agentmods" 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.00022 | $0.01297 |
| Opus 5 | $0.00011 | $0.00648 |
| Sonnet 5 | $0.00004 | $0.00259 |
| Haiku 4.5 | $0.00002 | $0.00130 |
Grade A, and why
dx-plan-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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-plan-review
An optional pre-implementation gate. Where dx-implement asks "did we build the plan?", this asks "will this plan actually work?" — a flawed plan costs hours, a flawed review costs minutes. Report only: you analyze and recommend, you never edit plan.md or the code it describes. Fixes are for the user or dx-plan to apply.
Guard. Resolve <change-id> under context/changes/; its plan.md must exist — if not, tell the user to run /dx-plan <change-id> first. If the path is under context/archive/, refuse: an archived change is done.
Load first
plan.mdfully, plus thechange.md(notetype) and anyresearch/,frame.md,diagnosis.mdit draws on.- The
plan-templatereference (invokedx-referenceswithplan-template) — so you know the shape a sound plan should have. context/standards/and theknowledge-layerreference (invokedx-referenceswithknowledge-layer) — you need the matching heuristic and the real catalog yourself to catch a standard the plan's own checklist missed, not just re-check what it already listed.- The
review-reportreference (invokedx-referenceswithreview-report) — the finding-ID/Resolutionschema and file convention shared withimpl-reviewandreview-triage. foundation/glossary.md— a one-line habit: judge naming against the project's established terms.- Conditional topics, gated on the change — not on which headers
plan.mdalready has (the same triggersdx-planstep 2 uses, checked against the diff scope,change.md'stype, andframe.md's who/what-it-affects): a wrongly-omitted section must be as reachable as a present-but-wrong one.- Change touches a schema, table, or persisted structure → load
plan-data-model. - Change adds/changes an endpoint, function signature, event, or message another caller depends
on → load
plan-api-contracts. - Change introduces an external call, a migration, or needs an undo path once shipped → load
plan-failure-modes.
- Change touches a schema, table, or persisted structure → load
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.
- 8d ago First seen · 59 lines · 22 tokens per session scan A 2bfdac2179e5
dx-plan-review is a skill published in the GitHub repository dikamilo/dx-workflow (5 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 1,297 once invoked, about $0.0001 per session on Opus 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
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…