Borrowing it
Nothing to install: this file belongs to DeL-TaiseiOzaki/claude-code-orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DeL-TaiseiOzaki/claude-code-orchestra/main/.claude/skills/feature/SKILL.mdgit clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestraWrote 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/del-taiseiozaki/claude-code-orchestra/feature)<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/feature"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/feature/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/del-taiseiozaki/claude-code-orchestra/feature"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00147 | $0.09051 |
| Opus 5 | $0.00073 | $0.04526 |
| Sonnet 5 | $0.00029 | $0.01810 |
| Haiku 4.5 | $0.00015 | $0.00905 |
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 4d 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 — 892 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature
One entry point for feature work, two modes:
- MODE=existing (old
/add-featurepath): the feature goes into an established codebase whose conventions are already known. No external research needed → Codex-direct scope → design → plan. - MODE=greenfield (old
/start-featurepath): a large or new feature that needs external research and parallel design → Agent Teams (Researcher + Architect) with bidirectional communication.
Both modes converge on a shared Phase 3: user approval + complexity-routed implementation.
Preflight: ensure codex CLI is current (see codex-system skill).
/feature <feature description>
| MODE determination (AskUserQuestion when ambiguous)
├─ MODE=existing : Phase 1E SCOPE -> Phase 2E DESIGN (Codex direct)
└─ MODE=greenfield : Phase 1G UNDERSTAND -> Phase 2G RESEARCH & DESIGN (Agent Teams)
| Phase 3 (shared): PLAN, APPROVE & IMPLEMENT
SIMPLE (1-3 files, <50 LOC) -> Codex danger-full-access direct
MODERATE (3-5 files) -> Codex danger-full-access + /team-execute --review-only
COMPLEX (5+ files) -> /team-execute (implement + review)
Mode Determination (always first)
Decide the MODE before anything else. Signals:
| Signal | MODE=existing | MODE=greenfield |
|---|---|---|
| Codebase state | Established, conventions known | New area, or conventions absent |
| External research needed | No — Codex reasons about existing patterns directly | Yes — libraries/tools/reference architectures must be researched |
| Feature size | Localized addition | Large, multi-module, or project kickoff |
| Design source | Codex (read-only consults) | Agent Teams (Researcher + Architect) |
If the signals are mixed or unclear, ask via AskUserQuestion — do NOT guess:
question: "Which feature mode applies?"
multiSelect: false
options:
- label: "existing"
description: "Add to an established codebase; conventions known; no external research (old /add-feature)."
- label: "greenfield"
description: "Large/new feature; needs external research and parallel design via Agent Teams (old /start-feature)."
What ships with it
2 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.
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 Changed 252ed9f2e8c2
- 10d ago First seen · 892 lines · 147 tokens per session scan A f8b29fda0265
feature is a skill published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (194 stars, last pushed 5d ago), licensed MIT. It adds 147 tokens to every session and 9,051 once invoked, about $0.0007 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.