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/specnpx skills add cryndoc/polisade-orchestrator --skill specgit 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/spec)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/spec"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/spec.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.00116 | $0.13161 |
| Opus 5 | $0.00058 | $0.06581 |
| Sonnet 5 | $0.00023 | $0.02632 |
| Haiku 4.5 | $0.00012 | $0.01316 |
Grade A, and why
spec 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 — 1,061 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:spec [PRD-XXX | FEAT-XXX] — Техническая спецификация через субагент
Создание технической спецификации на основе PRD или Feature Brief через изолированный субагент.
Использование
/polisade:spec PRD-001 # Спека для крупной инициативы
/polisade:spec FEAT-001 # Спека для фичи (если нужна архитектура)
/polisade:spec # Выбрать из доступных ready PRD/FEAT
/polisade:spec PRD-001 --story=ABC-1234 # → docs/specs/SPEC-NNN__ABC-1234__<slug>.md
Когда нужна спецификация
Нужна SPEC:
- Новые API endpoints
- Изменения в базе данных
- Сложная бизнес-логика
- Интеграция с внешними сервисами
- Архитектурные изменения
Не нужна SPEC (иди сразу в /polisade:tasks):
- UI изменения без логики
- Простые CRUD операции
- Багфиксы
- Мелкие улучшения
Архитектура с субагентом
┌─────────────────────────────────────────────────────────────┐
│ PM: /polisade:spec PRD-001 │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ ОСНОВНОЙ АГЕНТ │
│ 1. Валидация: PRD/FEAT со статусом ready │
│ 2. Читает PRD/FEAT файл полностью │
│ 3. Читает knowledge.json │
│ 4. Формирует prompt с системным промптом │
│ 5. Запускает Task tool: subagent_type="general-purpose" │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ СУБАГЕНТ general-purpose (чистый контекст) │
│ │
│ System role: Technical Specification Architect │
│ Input: PRD/FEAT content + project context │
│ │
│ Делает: │
│ 1. Анализирует требования │
│ 2. Выявляет технические gaps → вопросы (если есть) │
│ 3. Проектирует архитектуру │
│ 4. Создаёт SPEC файл по структуре │
│ 5. Возвращает: путь, summary, вопросы │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ ОСНОВНОЙ АГЕНТ │
│ 1. Если вопросы → статус waiting_pm │
│ 2. Если готово → обновляет PROJECT_STATE.json │
│ 3. Обновляет counters.json │
└─────────────────────────────────────────────────────────────┘
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 · 1,061 lines · 116 tokens per session scan A a66877df893c
spec is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 10d ago), licensed Apache-2.0. It adds 116 tokens to every session and 13,161 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
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…