A project setup command that creates the standard Polisade Orchestrator folders and files in your current project. It prepares shared state, documentation, templates, and a backlog.

Use it when starting a Polisade project or adding its structure to an existing repository. It creates state files, planning and architecture folders, and places for service contracts.

It removes the need to build the project-management structure by hand. For an existing codebase, it creates the structure without analysing the code.

init — Skill for Claude Code and Codex by cryndoc: A project setup command that creates the standard Polisade…

Install

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.

agentmods

npx agentmods add skills/cryndoc/polisade-orchestrator/init

Any agent

npx skills add cryndoc/polisade-orchestrator --skill init

Clone the repo

git clone --depth 1 https://github.com/cryndoc/polisade-orchestrator

Made for: Claude Code, Codex.

Or install polisade, the plugin that ships this one along with the rest of its 27 skills, 2 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/init.svg)](https://agentmods.dev/skills/cryndoc/polisade-orchestrator/init)

Your own site

<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/init"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/init.svg" alt="Measured on agentmods" height="20"></a>

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,165 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00089	$0.03165
Opus 5	$0.00044	$0.01582
Sonnet 5	$0.00018	$0.00633
Haiku 4.5	$0.00009	$0.00316

Measured 4d ago against content hash 082e3dd86634, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

init 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.

The scan reads SKILL.md. This mod also ships 2 executable files (templates/scripts/polisade_drift_gate.py, templates/scripts/polisade_spec_lint.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/init/SKILL.md · 283 lines

How it starts

The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/polisade:init — Initialize Polisade Orchestrator project structure

Scaffold the full Polisade Orchestrator autonomous development framework into the current project.

Brownfield-онбординг (если PM просит «онбординг репозитория» / зовёт прежнюю команду onboard / «заведи старый репозиторий»): такой команды больше нет — команда onboard удалена в 3.6.0, brownfield-онбординг (треки B0–B6, знание-производящая работа) — часть отдельного продукта Polisade Takt + Reverse, а не этого клиента. Ответь PM ровно это, без имитации онбординга. Для существующего репозитория здесь по-прежнему работает /polisade:init — он разворачивает структуру клиента (стейт, шаблоны, backlog), не анализируя код.

Usage

/polisade:init MyProject
/polisade:init              # uses current directory name

What it creates

.state/
├── PROJECT_STATE.json
├── counters.json
└── knowledge.json

docs/
├── prd/
├── specs/
├── plans/
├── adr/
├── architecture/   # design packages from /polisade:design
├── contracts/
│   ├── README.md       # integration map
│   ├── provided/       # contracts we provide (OpenAPI, AsyncAPI, Protobuf…)
│   └── consumed/       # contracts we consume from external systems (read-only)
└── templates/
    ├── prd-template.md
    ├── spec-template.md
    ├── plan-template.md
    ├── feature-brief-template.md
    ├── task-template.md
    ├── adr-template.md
    ├── chore-template.md
    ├── spike-template.md
    └── design-package-template.md

backlog/
├── features/
├── bugs/
├── tech-debt/
├── chores/
└── spikes/

tasks/

CLAUDE.md
.claude/settings.json
.gitignore (updated)

Algorithm

If $ARGUMENTS is provided, use it as project name. Otherwise use the current directory name.
Check if Polisade Orchestrator is already initialized:
- If .state/PROJECT_STATE.json exists → warn and ask to confirm overwrite

Create directory structure:

mkdir -p .state
mkdir -p docs/prd docs/specs docs/plans docs/architecture docs/architecture/decisions docs/contracts/provided docs/contracts/consumed docs/templates
mkdir -p docs/waivers
mkdir -p backlog/features backlog/bugs backlog/tech-debt backlog/chores backlog/spikes
mkdir -p tasks scripts
mkdir -p .claude .github/workflows
# Git does not track empty directories — without a placeholder, `git add` silently
# drops this scaffold and downstream skills (defect/feature/spec/...) then fail to
# place BUG-*/FEAT-*/SPEC-*/... artifacts in their canonical dirs (#122). The
# .gitkeep is harmless and goes away naturally once a real artifact lands.
touch docs/prd/.gitkeep docs/specs/.gitkeep docs/plans/.gitkeep docs/architecture/.gitkeep docs/architecture/decisions/.gitkeep
touch docs/waivers/.gitkeep
touch backlog/features/.gitkeep backlog/bugs/.gitkeep backlog/tech-debt/.gitkeep backlog/chores/.gitkeep backlog/spikes/.gitkeep
touch tasks/.gitkeep

Read the full file on GitHub · 283 lines

Files

What ships with it

23 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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 · 283 lines · 89 tokens per session scan A 082e3dd86634

Subscribe to this mod's changes

init is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 89 tokens to every session and 3,165 once invoked, about $0.0004 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.

Autonomous Agents LLM ai-agents claude-code claude-code-plugin developer-tools

deep-execution

Executes agent-enhanced council queries by spawning parallel Claude subagents that each query a provider, evaluate response quality, ask follow-up questions, and return structured insights with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or when complex architectural decisions…

hex/claude-council · 61 tokens

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…

jszmajda/lid · 105 tokens

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.

MarcoPorcellato/matryca-plumber · 47 tokens

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.

MarcoPorcellato/matryca-plumber · 45 tokens

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…

simonasrazm/simon-factory-lights-out · 74 tokens

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…

jszmajda/lid · 92 tokens