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 cryndoc/polisade-orchestrator --skill tasksgit 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/tasks)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/tasks"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/tasks/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/cryndoc/polisade-orchestrator/tasks"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 196 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 196 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 753 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 753 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.12338 |
| Opus 5.5 | $0.00051 | $0.04935 |
| Sonnet 5.5 | $0.00025 | $0.02468 |
| Haiku 4.5 | $0.00013 | $0.01234 |
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 13d 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 — 801 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. Номера выдаст /polisade:sync на транке │
└─────────────────────────────────────────────────────────────┘
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 16 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.4 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.
- 13d ago Changed e1f0ad126632
- 14d ago Changed · +3 lines 84951fd11d13
- 1mo ago Changed · +7 lines c43903fdb96f
- 1mo ago Changed · +32 lines 531a58ac5ee2
- 1mo 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 5d ago), licensed Apache-2.0. It adds 127 tokens to every session and 12,338 once invoked, about $0.0005 per session on Opus 5.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
autopilot-project
A project mode for managing a task DAG, a graph that shows which tasks depend on other tasks. It provides context for the /autopilot status and /autopilot next commands.
collaboration-workflow
Complete guide to the OpenSquad multi-agent collaboration system with user authorization gates. Use this skill when starting a collaboration session, coordinating multiple agents, managing the collaboration board, or when you need to understand how to use boardupdate, boardlist, and other collaboration tools. Triggers…
Collaboration Management
Complete guide to multi-agent collaboration card management, including starting collaborations, joining teams, and creating custom collaboration cards.
scout-briefing
Launch a Scout morning briefing session as a background process. Auto-detects mode (morning briefing, consolidation, or weekend briefing) from the current time and day.
autogpt-agents
Autonomous AI agent platform for building and deploying continuous agents. Use when creating visual workflow agents, deploying persistent autonomous agents, or building complex multi-step AI automation systems.
scout-dream
Launch a Scout dreaming session as a background process. Processes feedback, does KB deep work, and works on wishlist items.