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 triagegit 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/triage)<a href="https://agentmods.dev/skills/davekilleen/dex/triage"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/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/davekilleen/dex/triage"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/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.00077 | $0.03667 |
| Opus 5.5 | $0.00031 | $0.01467 |
| Sonnet 5.5 | $0.00015 | $0.00733 |
| Haiku 4.5 | $0.00008 | $0.00367 |
Grade A, and why
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 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cleanup and routing tool that finds standalone files and scattered tasks, then suggests where they belong using your current strategic context (Week Priorities + Quarterly Goals).
Execution Style
This skill handles quick decisions. Be concise. Don't over-analyze. Make a routing decision and move on. Target: <2 seconds of thinking per item.
What It Does
- Files: Routes standalone files in
00-Inbox/to projects, person pages, or resource folders - Tasks: Finds unchecked
- [ ]tasks scattered across notes and routes them appropriately - Strategic: Uses your Week Priorities and Quarterly Goals to inform routing confidence
Usage
/triage- Process everything (files + tasks)/triage files- Organize standalone files only/triage tasks- Extract and route tasks only
Arguments
$MODE: Optional. "files" | "tasks" | "all". Default: "all"
Step 0: Load Strategic Context & Structure Discovery
Before processing inbox items, load strategic context and build an index of existing entities. This makes triage strategically aware and enables intelligent routing.
0. Load Strategic Context
Read these files to understand current priorities:
-
Week Priorities:
02-Week_Priorities/Week_Priorities.md- Extract this week's Top 3 focus items
- Note any specific projects/people mentioned
- Capture keywords and themes
-
Quarterly Goals:
01-Quarter_Goals/Quarter_Goals.md- Extract current quarter's goals
- Note associated projects and outcomes
- Capture keywords and themes
This context will inform routing decisions - entries matching current priorities get higher confidence scoring and are surfaced first.
1. Scan Projects
List all files in 04-Projects/:
- Extract project name from filename (convert underscores to spaces)
- Read frontmatter if present for description, status, pillar
- Build index:
{ name, path, description, status, pillar }
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 e765daf3d88c
- 1mo ago Changed · +10 lines 6086110c4a0f
- 1mo ago First seen · 405 lines · 77 tokens per session scan A 55671dc79529
triage is a skill published in the GitHub repository davekilleen/Dex (508 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 3,667 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-03.
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.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
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…