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/defectnpx skills add cryndoc/polisade-orchestrator --skill defectgit 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/defect)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/defect"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/defect.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.00109 | $0.01453 |
| Opus 5 | $0.00055 | $0.00727 |
| Sonnet 5 | $0.00022 | $0.00291 |
| Haiku 4.5 | $0.00011 | $0.00145 |
Grade A, and why
defect 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 5d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:defect [описание] — Добавить баг
Быстрое добавление бага с автоматическим созданием TASK для исправления.
Использование
/polisade:defect Кнопка не работает на мобильных
/polisade:defect Ошибка 500 при загрузке большого файла
Алгоритм
-
Вычисли next-id для BUG и TASK по протоколу из
skills/tasks/references/compute-next-id.md(единый max по.state/counters.json,PROJECT_STATE.artifactIndexи file-scan). При Counter drift — АБОРТ с рекомендациейpython3 {plugin_root}/scripts/polisade_sync.py . --apply --yes. -
Write-guard. Перед
Writeпроверь, чтоbacklog/bugs/BUG-{N}-slug.mdиtasks/TASK-{N}-slug.mdне существуют и что ключейBUG-{N}/TASK-{N}нет вstate.artifactIndex. При коллизии — АБОРТ. -
Создай файл
backlog/bugs/BUG-XXX-slug.md -
Автоматически создай
tasks/TASK-XXX-slug.mdсо ссылкой на BUG (парный write-guard: проверка применяется к обоим файлам перед IO).⛔ КРИТИЧНО: TASK-файл ДОЛЖЕН быть ровно
tasks/TASK-XXX-*.mdв корневой папкеtasks/. НЕ вdocs/tasks/, НЕ вdocs/TASK-*.md, НЕ вbacklog/tasks/./polisade:implementищет таски ТОЛЬКО в корневойtasks/. Если папки нет —mkdir -p tasks. -
Спроси краткие уточнения (если нужно):
- "Как воспроизвести?"
- "Критичность: блокер / серьёзный / мелкий?"
-
Инкрементируй счётчики BUG и TASK (
counters.json[BUG] = N_bug,counters.json[TASK] = N_task). -
Обнови
.state/PROJECT_STATE.json:- Добавь BUG со статусом
ready - Добавь TASK со статусом
readyвreadyToWork
- Добавь BUG со статусом
-
Выведи подтверждение
Автоматическое создание TASK
ВАЖНО: Баг автоматически создаёт связанную TASK:
/polisade:defect Кнопка не работает на мобильных
Создаёт:
1. backlog/bugs/BUG-001-mobile-button.md (status: ready)
2. tasks/TASK-001-fix-mobile-button.md (status: ready, parent: BUG-001)
Это гарантирует единый workflow: /polisade:implement работает только с TASK.
Шаблон файла BUG
---
id: BUG-XXX
title: "[Описание]"
status: ready
created: YYYY-MM-DD
priority: P1
severity: medium # blocker | critical | major | minor
task: TASK-XXX # Связанная задача
---
# Bug: [Описание]
## Описание проблемы
[Описание из команды]
## Как воспроизвести
1. [Шаг 1]
2. [Шаг 2]
3. [Результат]
## Ожидаемое поведение
[Как должно работать]
## Фактическое поведение
[Что происходит]
## Окружение
- Браузер/платформа:
- Версия:
## Возможная причина
[Если очевидно]
## Критерии исправления
- [ ] Баг не воспроизводится
- [ ] Тест добавлен
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.
- 5d ago First seen · 181 lines · 109 tokens per session scan A 5ed44a293354
defect is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 109 tokens to every session and 1,453 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
deep-execution
Executes agent-enhanced council queries as one Workflow of parallel Claude analyst agents that each query a provider, evaluate response quality, ask follow-up questions, and return a schema-enforced analysis with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or when complex…
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…