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 reviewgit 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/review)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/review"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/review/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/review"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/review.svg" alt="Reviewed on agentmods" width="80" 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.00121 | $0.03847 |
| Opus 5 | $0.00060 | $0.01924 |
| Sonnet 5 | $0.00024 | $0.00769 |
| Haiku 4.5 | $0.00012 | $0.00385 |
Grade A, and why
review 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 yesterday.
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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:review [TASK-XXX] [self] — TASK Quality Review (external CLI or self)
"Второе мнение" по качеству постановки задачи. По умолчанию — внешний reviewer CLI (Codex / OpenAI). С флагом self — CLI текущего агента (Claude Code / Codex / Qwen CLI) в отдельном процессе с чистым контекстом.
Read-only — ничего не модифицируется. Это advisory review.
Флаг
self— для случаев, когда доступна подписка только на один агент. Ревью проводится тем же CLI, но в изолированном процессе (чистый контекст = более независимое мнение, чем self-review в текущей сессии).
Использование
/polisade:review TASK-001 # Review через reviewer CLI (auto-select)
/polisade:review # Auto-select первый ready TASK
/polisade:review TASK-001 self # Review через текущий агент
/polisade:review self # Auto-select + self-review
Архитектура
/polisade:review TASK-001
|
v
+-----------------------------------------+
| ОСНОВНОЙ АГЕНТ |
| 1. Определить TASK-ID |
| (аргумент или auto-select ready) |
| 2. Запустить субагент |
+-----------------+-----------------------+
v
+-----------------------------------------+
| СУБАГЕНТ (general-purpose) |
| Bash: codex exec (или CLI агента при |
| self) из корня проекта |
| Ревьюер сам: |
| - Находит TASK файл |
| - Определяет parent из frontmatter |
| - Читает гайдлайны из корня проекта |
| - Читает код/тесты при необходимости |
| Возвращает текст ревью |
+-----------------+-----------------------+
v
+-----------------------------------------+
| ОСНОВНОЙ АГЕНТ |
| Показать результат в формате box |
+-----------------------------------------+
Алгоритм
1. Определить TASK-ID и режим
⛔ Вызов скрипта отклонён или не запустился (
Command references protected path/Install directory is read-protected/Filesystem Guard/the tool's default permission is 'deny', отказ песочницы, ненулевой exit без вывода) — STOP. Процитируй отказ дословно. НЕ пересказывай по исходнику, что скрипт «сделал бы»; НЕ собирай dry-run вручную; НЕ переходи к apply/push/pr-create. НЕ транскрибируй скрипт (прочитать → записать копию в/tmpили в проект → запустить копию): копия не байт-идентична — уезжают классы символов в regex, форма возврата функций, пропадают целые функции — и молча меняется набор применённых изменений. Отказ инструмента — это отказ, а не результат. Доложи PM дословный текст отказа и сошлись на #127 (доставка скриптов в проект).
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.
- yesterday Changed · +47 lines 468b78cb71f6
- 9d ago First seen · 233 lines · 121 tokens per session scan A 3604edbd114d
review is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed today), licensed Apache-2.0. It adds 121 tokens to every session and 3,847 once invoked, about $0.0006 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
audit
This skill should be used when the user asks to "audit spec coverage", "find uncovered modules", "scan for missing specs", "check wyx coverage", "get spec TODO list", "wyx audit", "wyx", or wants a prioritized list of wyx skill commands for uncovered modules. Scans for coverage gaps, pipeline/sync candidates, and…
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.
spawn-reviewers
Spawn and collect the reviewer fleet at stage20spawnreviewers. Consumes spawn.json.spec (the authoritative spawn spec from derive-spawn-spec / derive-static-spec), resolves GRAPHPROJECT, builds per-agent prompts from the per-agent template + role suffixes (Bug Hunter A/B, Unified Auditor, Domain Critics, Impact…
pr-reviewer
Reviews a diff or security scope read-only using evidence-tiered findings, structural and context-error rubrics, and repository review policy. Use when asked to "review my changes", "structural review", "review for AI patterns", or "security audit". For applying fixes use tidy; for UI defects use ui-design.
verify-findings
Dispatch and collect the finding-verifier fleet at stage23verifyfindings (PLN-722). Reads verifymanifest.json (written by stage22bverifyprepare), spawns one falsify-oriented verifier Task per toverify[] entry with mode-specific Task scheduling (GitHub mode dispatches verifiers synchronously; local mode uses parallel…
codex-review
Run Codex to review a plan file and return structured feedback with a verdict. Triggers on: debate loop Codex review rounds. Returns VERDICT:APPROVED or VERDICT:NEEDSCHANGES plus CODEXSESSION token.