Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cryndoc/polisade-orchestrator/plugin install polisadeWrote 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/tasks)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/tasks"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/tasks.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.00127 | $0.11410 |
| Opus 5 | $0.00063 | $0.05705 |
| Sonnet 5 | $0.00025 | $0.02282 |
| Haiku 4.5 | $0.00013 | $0.01141 |
Grade A, and why
tasks scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(`<test-command> --filter …`, `curl …`, компиляция целевого модуля), How it starts
The opening of the file, as written. The whole thing — 759 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:tasks [PLAN-XXX | SPEC-XXX | FEAT-XXX | BUG-XXX | DEBT-XXX | CHORE-XXX] — Создание задач через субагент
Создание атомарных задач из плана, спецификации, Feature Brief, Bug Report, Tech Debt или Chore через изолированный субагент.
Использование
/polisade:tasks PLAN-001 # Задачи из детального плана (итерация по items)
/polisade:tasks SPEC-001 # Задачи из спецификации
/polisade:tasks FEAT-001 # Задачи напрямую из фичи (для простых случаев)
/polisade:tasks BUG-001 # Задача из бага (обычно 1 TASK)
/polisade:tasks DEBT-001 # Задачи из техдолга (обычно 1-3 TASK)
/polisade:tasks CHORE-001 # Задача из chore (обычно 1 TASK)
/polisade:tasks # Выбрать из доступных ready артефактов
Когда что использовать
| Источник | Когда использовать | Типичное кол-во TASKs |
|---|---|---|
| PLAN | Крупная инициатива с фазами и зависимостями | 5-20 |
| SPEC | Техническая работа, требующая архитектуры | 3-10 |
| FEAT | Простая фича, понятная из описания | 2-5 |
| BUG | Багфикс с конкретным воспроизведением | 1 (реже 2-3) |
| DEBT | Рефакторинг, обычно ленивая декомпозиция после регистрации | 1-3 |
| CHORE | Простая задача, когда --no-task использовался при регистрации |
1 |
Архитектура с субагентом
Для PLAN (итерация по roadmap items)
┌─────────────────────────────────────────────────────────────┐
│ PM: /polisade:tasks PLAN-001 │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ ОСНОВНОЙ АГЕНТ │
│ 1. Валидация: PLAN со статусом ready │
│ 2. Читает PLAN + SPEC + PRD │
│ 3. Извлекает список roadmap items │
│ 4. Запускает субагенты для ВСЕХ items (параллельно) │
└─────────────────────────────────────────────────────────────┘
│
┌───────────┼───────────┐
▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ СУБАГЕНТ │ │ СУБАГЕНТ │ │ СУБАГЕНТ │
│ Item MVP-1.1 │ │ Item MVP-1.2 │ │ Item MVP-2.1 │
│ → 3 TASKs │ │ → 2 TASKs │ │ → 4 TASKs │
└───────────────┘ └───────────────┘ └───────────────┘
│ │ │
└───────────┼───────────┘
▼
┌─────────────────────────────────────────────────────────────┐
│ ОСНОВНОЙ АГЕНТ │
│ 1. Собирает ВСЕ TASK в память (НЕ сохраняет файлы) │
│ 2. Consolidated PM Checkpoint (один на весь PLAN) │
│ 3. После подтверждения — сохраняет файлы │
│ 4. Обновляет PROJECT_STATE.json │
│ 5. Обновляет counters.json │
└─────────────────────────────────────────────────────────────┘
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/checkpoint-format.md 2.8 KB
- references/compute-next-id.md 11 KB
- references/output-examples.md 2.5 KB
- references/prompt-bug-debt-chore.md 7.6 KB
- references/prompt-coordinate-task.md 13 KB
- references/prompt-plan-item.md 20 KB
- references/prompt-spec-feat.md 8.5 KB
- references/task-template-example.md 2.1 KB
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.
- 6d ago First seen · 759 lines · 127 tokens per session scan A aaba08ca7a72
tasks is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 10d ago), licensed Apache-2.0. It adds 127 tokens to every session and 11,410 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
cvpr-iccv-eccv
CVPR / ICCV / ECCV paper formatting — activate when the user wants to submit to CVPR, ICCV, or ECCV, follow their template, or fix format issues for these computer vision conferences.