Borrowing it
Nothing to install: this file belongs to InteliGHQ/intelig-agent-playbook. 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/InteliGHQ/intelig-agent-playbook/main/.claude/commands/new-feature.mdgit clone --depth 1 https://github.com/InteliGHQ/intelig-agent-playbookWrote 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/commands/intelighq/intelig-agent-playbook/new-feature)<a href="https://agentmods.dev/commands/intelighq/intelig-agent-playbook/new-feature"><img src="https://agentmods.dev/badge/commands/intelighq/intelig-agent-playbook/new-feature.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.00021 | $0.00326 |
| Opus 5 | $0.00010 | $0.00163 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
new-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.
What it actually says
Create a new feature work-item for: $ARGUMENTS
Do this:
- Determine the target domain (bounded context) and a short kebab-case
<work-item>slug from the description. If it's unclear which existing domain owns this, ask before scaffolding. - Read
product/domains/customer/work-items/register-customer/to mirror the work-item shape exactly (README, requirements, design, tasks, acceptance), andproduct/domains/customer/README.mdfor the domain-overview shape. - Read
standards/STANDARDS_INDEX.mdand the families this feature will touch. - Hand off to the architect subagent to produce the four files in
product/domains/<domain>/work-items/<work-item>/. If the domain is new, the architect creates itsREADME.mdcontext overview first. The architect must fill in real content — a user story, EARS acceptance criteria, a domain model with cited rule IDs, a phased task table, and a hard "what this is NOT" boundary. No placeholders. - Map the feature to an initiative in
product/initiatives.md(or propose a new one if none fits — but keep initiatives coarse, a handful per quarter).
Stop after the spec exists. Do not write implementation code — that's a separate session driven by the spec you just wrote.
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.
- 6d ago First seen · 26 lines · 21 tokens per session scan A 6cec303ebdde
new-feature is a command published in the GitHub repository InteliGHQ/intelig-agent-playbook (2 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 326 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.