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.
git clone --depth 1 https://github.com/dapi/claude-code-marketplaceWrote 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/commands/dapi/claude-code-marketplace/route-task)<a href="https://agentmods.dev/commands/dapi/claude-code-marketplace/route-task"><img src="https://agentmods.dev/badge/commands/dapi/claude-code-marketplace/route-task/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/commands/dapi/claude-code-marketplace/route-task"><img src="https://agentmods.dev/badge/commands/dapi/claude-code-marketplace/route-task.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.00022 | $0.02371 |
| Opus 5.5 | $0.00009 | $0.00948 |
| Sonnet 5.5 | $0.00004 | $0.00474 |
| Haiku 4.5 | $0.00002 | $0.00237 |
Grade A, and why
route-task 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/route-task — Маршрутизация задачи в workflow
Version: 1.0.0
Получает ссылку на задачу или путь к локальному файлу, классифицирует через haiku-агента и запускает подходящий workflow разработки.
Перед началом работы покажи пользователю: route-task v1.0.0
Фаза 1: Валидация входных данных
Проверь $ARGUMENTS:
- Если пусто — спроси пользователя: "Укажи ссылку на задачу (GitHub Issue URL, Google Doc URL, URL, путь к файлу) или ссылку на issue (#123)"
- Извлечь флаг
--new-session: если$ARGUMENTSсодержит--new-session, запомниNEW_SESSION=trueи удали флаг из строки аргументов. ИначеNEW_SESSION=false. Флаг означает, что эта сессия уже выделенная (запущена в отдельной вкладке/окне) и предлагать "открыть новую сессию" не нужно. - Обрезать пробелы. Если несколько аргументов — использовать первый.
- Если аргумент начинается с
github.comилиdocs.google.com(без протокола) — добавитьhttps://. - Если аргумент начинается с
/,~/, или./— это путь к локальному файлу:- Раскрыть
~/до абсолютного пути (заменить~на домашнюю директорию). - Проверить существование файла через Read tool (прочитать первые 5 строк).
- Если файл не найден — покажи: "Файл не найден: {path}. Проверь путь и повтори." и останови выполнение.
- Если файл найден — переходи к Фазе 2.
- Раскрыть
- Если не похоже на URL (
http://,https://) и не является ссылкой на issue (#NNN) и не является локальным путём — покажи: "Неверный формат. Укажи URL (http:// или https://), путь к файлу (/path/to/plan.md) или ссылку на issue (#123)." и останови выполнение. - Если формат корректный — переходи к Фазе 2.
Фаза 2: Классификация задачи
Запусти субагент-классификатор через Task tool:
Task:
subagent_type: "task-router:task-classifier"
description: "Classify task for routing"
prompt: "Classify this task and determine the best workflow route: $ARGUMENTS"
model: haiku
max_turns: 10
Если Task tool завершился ошибкой (таймаут, crash, модель недоступна) — покажи: "Не удалось классифицировать задачу. Агент-классификатор не запустился. Попробуй позже: /route-task {url}" и останови выполнение.
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 First seen · 209 lines · 22 tokens per session scan A 98e17ad1d775
route-task is a command published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,371 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.