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/cryndoc/polisade-orchestrator/roadmapnpx skills add cryndoc/polisade-orchestrator --skill roadmapgit clone --depth 1 https://github.com/cryndoc/polisade-orchestratorWrote 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/cryndoc/polisade-orchestrator/roadmap)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/roadmap"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/roadmap.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.00109 | $0.06946 |
| Opus 5 | $0.00055 | $0.03473 |
| Sonnet 5 | $0.00022 | $0.01389 |
| Haiku 4.5 | $0.00011 | $0.00695 |
Grade A, and why
roadmap 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 5d 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 — 693 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:roadmap [SPEC-XXX] — План реализации через субагент
Создание плана реализации на основе технической спецификации через изолированный субагент.
Использование
/polisade:roadmap SPEC-001 # План для конкретной спеки
/polisade:roadmap # Выбрать из доступных ready SPEC
Когда нужен roadmap
Нужен PLAN:
- Крупная инициатива с несколькими фазами
- Сложные зависимости между задачами
- Работа на несколько недель
- Требуется координация компонентов
Не нужен PLAN (иди сразу в /polisade:tasks):
- Простая фича (2-5 задач)
- Линейная последовательность работ
- Нет сложных зависимостей
Архитектура с субагентом
┌─────────────────────────────────────────────────────────────┐
│ PM: /polisade:roadmap SPEC-001 │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ ОСНОВНОЙ АГЕНТ │
│ 1. Валидация: SPEC со статусом ready │
│ 2. Читает SPEC + связанный PRD │
│ 3. Читает knowledge.json │
│ 4. Формирует prompt с системным промптом │
│ 5. Запускает Task tool: subagent_type="general-purpose" │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ СУБАГЕНТ general-purpose (чистый контекст) │
│ │
│ System role: Product Delivery Roadmap Architect │
│ Input: SPEC + PRD + project context │
│ │
│ Делает: │
│ 1. Анализирует техническую спецификацию │
│ 2. Разбивает на логические фазы │
│ 3. Определяет roadmap items с зависимостями │
│ 4. Выявляет критический путь │
│ 5. Создаёт PLAN файл │
│ 6. Возвращает: путь, summary, items count │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ ОСНОВНОЙ АГЕНТ │
│ 1. Обновляет PROJECT_STATE.json │
│ 2. Обновляет counters.json │
│ 3. SPEC.children += PLAN (статус НЕ меняется) │
└─────────────────────────────────────────────────────────────┘
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.
- 5d ago First seen · 693 lines · 109 tokens per session scan A cc64248f2508
roadmap is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 10d ago), licensed Apache-2.0. It adds 109 tokens to every session and 6,946 once invoked, about $0.0005 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
deep-execution
Executes agent-enhanced council queries as one Workflow of parallel Claude analyst agents that each query a provider, evaluate response quality, ask follow-up questions, and return a schema-enforced analysis with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or when complex…
update-lid
Configure or reconcile a project for linked-intent development (LID). Dispatches on project state — fresh bootstrap, append directives to an existing agent-instructions file (AGENTS.md or CLAUDE.md), add missing mode marker, reconcile convention drift, or run mode transitions. Invoked as /update-lid. For fresh…
matryca-github
Apply Matryca maintainer standards for GitHub issues, pull requests, branches, reviews, merges, milestones, tags, releases, and remote comments. Use before any GitHub-facing action or artifact.
matryca-logseq-io
Choose safe direct-file versus Local HTTP API access for Logseq. Use when changing graph reads, writes, background indexing, live Logseq integration, authentication, or JSON-RPC communication.
sflo
Starts and manages SFLO factory runs through the configured runner. Use when the user explicitly asks to start, run, resume, list, kill, clean, or inspect an SFLO factory, including requests to build something with SFLO. Do not use when SFLO appears only in quoted text, documentation, examples, code, logs, or…
map-codebase
Bootstrap LID in an existing (brownfield) codebase. Deep-reads every file in the declared scope, offers lens-based clustering options, generates skeleton LLDs/HLD/EARS bottom-up, then creates arrow docs and prompts the user to flesh out the skeletons. Token-intensive by design. Use when asked to map a codebase…