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 agentmods add skills/dcramer/dex/dex-plannpx skills add dcramer/dex --skill dex-plangit clone --depth 1 https://github.com/dcramer/dexWhat 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 | $0.00021 | $0.02991 |
| Opus 5 | $0.00010 | $0.01496 |
| Sonnet 5 | $0.00004 | $0.00598 |
| Haiku 4.5 | $0.00002 | $0.00299 |
Grade A, and why
dex-plan 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 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.
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 — 510 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Converting Markdown Documents to Tasks
Command Invocation
Use dex directly for all commands:
dex <command>
If dex is not on PATH, use npx @zeeg/dex <command> instead. Check once at the start:
command -v dex &>/dev/null && echo "use: dex" || echo "use: npx @zeeg/dex"
Use /dex-plan to convert any markdown planning document into a trackable dex task.
When to Use
- After completing a plan in plan mode
- Converting specification documents to trackable tasks
- Converting design documents to implementation tasks
- Creating tasks from roadmap or milestone documents
- Tracking any markdown planning or design content
Supported Documents
Any markdown file containing planning or design content:
- Plan files from plan mode (
~/.claude/plans/*.md) - Specification documents (
SPEC.md,REQUIREMENTS.md) - Design documents (
DESIGN.md,ARCHITECTURE.md) - Roadmaps and milestone documents (
ROADMAP.md) - Feature proposals and technical RFCs
Usage
/dex-plan <markdown-file-path>
Examples
From plan mode:
/dex-plan /home/user/.claude/plans/moonlit-brewing-lynx.md
From specification document:
/dex-plan @SPEC.md
From design document:
/dex-plan docs/AUTHENTICATION_DESIGN.md
From roadmap:
/dex-plan ROADMAP.md
What It Does
- Reads the markdown file
- Extracts title from first
#heading (or uses filename as fallback) - Strips "Plan: " prefix if present (case-insensitive)
- Creates dex task with full markdown content as context
- Analyzes plan structure for potential subtask breakdown
- Automatically creates subtasks when appropriate
- Returns task ID and breakdown summary
Examples
From plan mode file:
# Plan: Add JWT Authentication
## Summary
...
→ Task description: "Add JWT Authentication" (note: "Plan: " prefix stripped)
From specification document:
# User Authentication Specification
## Requirements
...
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 First seen · 510 lines · 21 tokens per session scan A 030a89261fa3
dex-plan is a skill published in the GitHub repository dcramer/dex (378 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 2,991 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-30.
Other skills, from other repositories
execute
Carry an approved task through to working, verified code.
backlog-technical-project-manager
Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization…
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
kanban-tui
Comprehensive kanban board and task management via ktui CLI. Use for project tracking, todo lists, task dependencies, workflow automation, and board management. Activates when user mentions boards, tasks, kanban, or project management. If the ktui command is not available, but uv is available utilize uvx kanban-tui…
at-zentao
Handle ZenTao (禅道) Bugs and Tasks end to end, including updating or writing back an item after code changes, managing Task status and hours, and reading linked Stories. Use for referenced ZenTao items, requirements, status changes, time entries, or post-implementation synchronization.
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.