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 choregit 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/chore)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/chore"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/chore.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.00106 | $0.01919 |
| Opus 5 | $0.00053 | $0.00959 |
| Sonnet 5 | $0.00021 | $0.00384 |
| Haiku 4.5 | $0.00011 | $0.00192 |
Grade A, and why
chore 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 7d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:chore [описание] [--no-task] — Простая задача
Быстрое добавление простой задачи, не требующей планирования. По умолчанию
создаёт пару CHORE + TASK (TASK идёт в readyToWork). Передай --no-task,
чтобы только зарегистрировать chore без TASK.
Использование
/polisade:chore Увеличить контекстное окно до 128k
/polisade:chore Обновить README с новыми командами
/polisade:chore Удалить неиспользуемые зависимости
/polisade:chore Поправить форматирование в конфиге --no-task # только регистрация
- Default — как раньше: CHORE + TASK сразу. CHORE по определению «< 1 часа, очевидная реализация», поэтому «сделать сейчас» — типичное намерение.
- С
--no-task— только CHORE со статусомready; для последующей декомпозиции используй/polisade:tasks CHORE-XXX.
Категории
| Категория | Примеры |
|---|---|
config |
Изменение конфигурации, переменных окружения |
cleanup |
Удаление мусора, неиспользуемого кода |
upgrade |
Обновление версий, миграции |
docs |
Обновление документации (не создание новой) |
Алгоритм
- Распарсь args. Выдели
--no-task(если есть), остаток склей в описание. - Прочитай
.state/PROJECT_STATE.json. Извлекиsettings.chore.autoCreateTask(default:trueесли ключ отсутствует). - Определи
create_task:create_task = settings.chore.autoCreateTask and (not --no-task).- Флаг
--no-taskпобеждает настройку (и наоборот, если настройкаfalse, то флаг не нужен — TASK и так не создастся).
- Вычисли next-id для CHORE по протоколу из
skills/tasks/references/compute-next-id.md. Еслиcreate_task— также вычисли next-id для TASK. При Counter drift — АБОРТ с рекомендациейpython3 {plugin_root}/scripts/polisade_sync.py . --apply --yes. - Write-guard. Перед
Writeпроверь, чтоbacklog/chores/CHORE-{N}-slug.mdне существует иCHORE-{N}отсутствует вstate.artifactIndex. Еслиcreate_task— та же проверка наtasks/TASK-{M}-slug.md/TASK-{M}. При коллизии — АБОРТ. - Создай файл
backlog/chores/CHORE-XXX-slug.md. - Если
create_task— создайtasks/TASK-XXX-slug.mdсо ссылкой на CHORE.
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.
- 7d ago First seen · 179 lines · 106 tokens per session scan A 699a1c04fcac
chore is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 11d ago), licensed Apache-2.0. It adds 106 tokens to every session and 1,919 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
shiploop
Self-improving multi-agent harness: wraps N git sub-repos as one workspace, dispatches named tickets to cheap-floor headless agents that escalate once on failure, promoting lessons into CLAUDE.md. Use when working in or scaffolding a meta-repo workspace (sub-folders each own .git; root has scripts/ + queue/tickets.md…
ungate-queue
Use when the user wants to work THROUGH the blocked items on a queue with you present — "unblock these", "walk me through what is gated", "let us clear the questions" — or immediately after an unattended run reports items it could not do. Turns each gate reason into the single question that would release the item…
autopilot
Use when the user asks to run a whole queue of open work unattended — "autopilot", "run everything you can", "clear what you can while I am away", "full auto on my open items". Orchestrates the complete run as an explicit checklist: triage the queue into tiers, execute the autonomous pile without stopping, then close…
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.