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 davekilleen/Dex --skill dex-backloggit clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/dex-backlog)<a href="https://agentmods.dev/skills/davekilleen/dex/dex-backlog"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/dex-backlog/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/davekilleen/dex/dex-backlog"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/dex-backlog.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.00069 | $0.04370 |
| Opus 5.5 | $0.00028 | $0.01748 |
| Sonnet 5.5 | $0.00014 | $0.00874 |
| Haiku 4.5 | $0.00007 | $0.00437 |
Grade A, and why
dex-backlog 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 1mo 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 — 648 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What This Command Does
In plain English: AI-powered ranking of your Dex system improvement backlog based on current system state. Shows you what to build next.
When to use it:
- Weekly check-in on system improvements
- After capturing several new ideas
- When deciding what to work on next
- During quarterly planning for system improvements
How to run it:
/dex-backlog # Full review with re-ranking
Process Overview
- Load context - Read system state, usage patterns, learnings
- Score ideas - Calculate 5-dimension scores for each idea
- Re-rank backlog - Sort by weighted total score
- Update file - Write new rankings to
System/Dex_Backlog.md - Present top ideas - Show top 5 with "Why now?" justification
- Offer next steps - Workshop, implement, or defer
Step 1: Load System Context
Read these files to understand current system state:
Required Files
System/Dex_Backlog.md # All ideas to score
System/usage_log.md # Feature adoption patterns
System/user-profile.yaml # Role, preferences
CLAUDE.md # Current capabilities
Optional Files (if they exist)
System/Session_Learnings/ # Recent pain points (last 30 days)
.claude/commands/ # Available commands
core/mcp/ # MCP integrations
06-Resources/Learnings/ # Captured patterns
Extract Context
Build a context dictionary with:
- Usage patterns: Which features are used vs. unused
- Role profile: PM, Sales, Leadership, Engineer, etc.
- Pain points: Recent friction from session learnings
- System capabilities: What's currently available
- Backlog state: All ideas and their current scores
Step 2: Score Each Idea
For every active idea in the backlog, calculate 5 dimension scores.
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.
- 1mo ago Changed d52e024c176e
- 1mo ago First seen · 648 lines · 69 tokens per session scan A d5c85e80e55c
dex-backlog is a skill published in the GitHub repository davekilleen/Dex (507 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 4,370 once invoked, about $0.0003 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-09-02.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…