feature

feature is a skill for Claude Code from cryndoc/polisade-orchestrator. It costs 117 tokens per session (1,471 once invoked), scanned A, original, Apache-2.0.

A short Feature Brief writer for small or medium product changes. It records what the feature should do without the heavier process used for a full Product Requirements Document.

In plain words
What is it for?
Use it for requests such as adding an export button or a sharing action. It creates a feature file, asks about priority and size, and records the basic work needed.
Why use it?
It gives a small piece of work a clear description and tracking ID without making the team complete a lengthy planning document. It also checks for duplicate IDs before creating the brief.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the polisade plugin — 27 skills, 2 commands shipped together

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/feature
Any agent
npx skills add cryndoc/polisade-orchestrator --skill feature
Clone the repo
git clone --depth 1 https://github.com/cryndoc/polisade-orchestrator

Made for: Claude Code.

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.

agentmods badge for feature

README.md
[![agentmods](https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/feature.svg)](https://agentmods.dev/skills/cryndoc/polisade-orchestrator/feature)
Your own site
<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/feature"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/feature.svg" alt="Measured on agentmods" height="20"></a>
Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,471 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00117 $0.01471
Opus 5 $0.00059 $0.00736
Sonnet 5 $0.00023 $0.00294
Haiku 4.5 $0.00012 $0.00147

Measured 6d ago against content hash 00608ba25030, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

feature 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 6d 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.

skills/feature/SKILL.md · 176 lines

How it starts

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

/polisade:feature [описание] — Добавить фичу

Создание Feature Brief — короткого описания фичи для быстрой работы.

Это основной способ добавления фич. Используй PRD только для крупных инициатив.

Использование

/polisade:feature Добавить экспорт в PDF
/polisade:feature Кнопка "Поделиться" в карточке товара

Алгоритм

Быстрое добавление (по умолчанию)

Если PM даёт короткое описание:

  1. Вычисли next-id для FEAT по протоколу из skills/tasks/references/compute-next-id.md (единый max по .state/counters.json, PROJECT_STATE.artifactIndex и file-scan backlog/features/FEAT-*.md). При Counter drift — АБОРТ с рекомендацией python3 {plugin_root}/scripts/polisade_sync.py . --apply --yes.
  2. Write-guard. Перед Write проверь, что backlog/features/FEAT-{N}-slug.md не существует и что FEAT-{N} нет в state.artifactIndex. При коллизии — АБОРТ.
  3. Создай файл backlog/features/FEAT-XXX-slug.md
  4. Заполни базовую информацию
  5. Спроси 2-3 уточняющих вопроса:
    • "Какой приоритет: P1 (высокий), P2 (средний), P3 (низкий)?"
    • "Это на несколько часов (S), дней (M) или неделю+ (L)?"
    • Если непонятно: "Можешь описать что именно должно происходить?"
  6. Инкрементируй счётчик (counters.json[FEAT] = N).
  7. Обнови PROJECT_STATE.json
  8. PM Checkpoint для M/L (см. ниже)
  9. Покажи результат с рекомендацией следующего шага

Определение размера (size)

Size Описание Следующий шаг
S Несколько часов, очевидная реализация /polisade:tasks сразу
M Несколько дней, понятные требования /polisade:tasks или /polisade:spec
L Неделя+, сложная логика Предложи /polisade:prd

PM Checkpoint

Для size M или L — ОБЯЗАТЕЛЬНАЯ остановка:

═══════════════════════════════════════════
НУЖНО РЕШЕНИЕ PM
═══════════════════════════════════════════
Контекст: FEAT-001 (Экспорт в PDF)
Размер: M (несколько дней)

Вопрос: Нужна ли техническая спецификация?

1. Да — создать SPEC для проработки архитектуры
2. Нет — сразу /polisade:tasks для создания задач

Рекомендация: 2 (для M достаточно задач)

→ "1" / "2" или "continue" для рекомендации
═══════════════════════════════════════════

Read the full file on GitHub · 176 lines

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.

  1. 6d ago First seen · 176 lines · 117 tokens per session scan A 00608ba25030

Subscribe to this mod's changes

feature is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 10d ago), licensed Apache-2.0. It adds 117 tokens to every session and 1,471 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.

Related

Other skills, from other repositories

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

cvpr-iccv-eccv

CVPR / ICCV / ECCV paper formatting — activate when the user wants to submit to CVPR, ICCV, or ECCV, follow their template, or fix format issues for these computer vision conferences.

nanoAgentTeam/research-claw · 52 tokens