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/continuenpx skills add cryndoc/polisade-orchestrator --skill continuegit 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/continue)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/continue"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/continue.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 | $0.00011 | $0.07029 |
| Opus 5 | $0.00005 | $0.03514 |
| Sonnet 5 | $0.00002 | $0.01406 |
| Haiku 4.5 | $0.00001 | $0.00703 |
Grade A, and why
continue 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 4d 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 — 661 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:continue — Автономная работа
Найти готовые к работе артефакты и выполнять их автономно.
⛔ КРИТИЧЕСКИ ВАЖНО: Полный цикл обязателен!
┌─────────────────────────────────────────────────────────────┐
│ ⛔ ЗАПРЕЩЕНО ставить status: done если: │
│ │
│ ✗ Regression tests НЕ прогнаны │
│ ✗ PR НЕ создан │
│ ✗ Review НЕ пройден │
│ ✗ Merge НЕ выполнен │
│ │
│ После написания кода статус: in_progress │
│ После создания PR статус: review │
│ После merge PR статус: done │
└─────────────────────────────────────────────────────────────┘
Каждая TASK проходит ПОЛНЫЙ ЦИКЛ:
1. IMPLEMENT → код + unit tests + commit → статус: in_progress
2. REGRESSION → запуск ВСЕХ тестов проекта → исправить если упали
3. CREATE PR → push + pr-create (polisade_vcs.py) → статус: review
4. REVIEW LOOP → ждать/исправлять → повторять до approve
5. MERGE → pr-merge + delete-branch → статус: done
НЕ ПЕРЕХОДИ к следующей TASK пока текущая не завершена полностью!
Использование
/polisade:continue # Начать автономную работу
Алгоритм
- Прочитай
.state/PROJECT_STATE.json - Прочитай
.state/knowledge.jsonдля контекста проекта - Проверь
waitingForPM:- Если не пусто → "Есть N вопросов к тебе. Запусти /polisade:unblock сначала."
- Проверь
readyToWork:- Если пусто → "Всё сделано или заблокировано. /polisade:state для деталей."
- Если
workspaceMode: "worktree":- Выполни
git worktree list --porcelain - Извлеки ветки активных worktree
- Сопоставь ветки → TASK-ID (по конвенции именования)
- Пропусти задачи с активным worktree (заняты другим агентом)
- Выполни
- Выбери задачу по приоритету (см. ниже)
- Выполни ПОЛНЫЙ ЦИКЛ для задачи (см. ниже)
- Повтори с шага 1
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.
- 4d ago First seen · 661 lines · 11 tokens per session scan A f016cfbd78eb
continue is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 11 tokens to every session and 7,029 once invoked, about $0.0001 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
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…
Collaboration Management
Complete guide to multi-agent collaboration card management, including starting collaborations, joining teams, and creating custom collaboration cards.
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…
product-discovery
File-first orchestrator for product discovery and spec frameworks. Frames the problem with a Discovery Lead, Product Analyst, or System Architect role. Spawns parallel framework agents (Double Diamond, How Might We, Jobs to Be Done, user stories with INVEST, EARS for AI-coder specs, Gherkin), synthesizes into a PRD or…
triage-for-autonomy
Use BEFORE starting an unattended run, to score an existing queue of open items — a to-do list, an issue tracker, plan steps, or a persistent open-items store — into what is safe to do now, what is autonomous but heavy, and what is gated on a human. Produces a tier verdict plus a gate reason per item, and ranks the…
update
Updates the vendored Sprint chain in bootstrapped repos from the plugin source. Refreshes scripts, subagents, MCP config, and git hooks. Use --all to update every registered repo. Leaves configuration and lifecycle files untouched.