feature-development

feature-development is a command for Claude Code from affaan-m/ECC. It costs 12 tokens per session (193 once invoked), scanned A, original, MIT.

A workflow command scaffold for implementing a software feature.

In plain words
What is it for?
Use it for feature work involving implementation, tests, API code, schemas, manifests, or documentation.
Why use it?
It gives the agent a repeatable sequence for understanding the change, editing the relevant code, checking it, and documenting the result.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the ecc plugin — 78 skills, 58 commands, 70 agents, 1 MCP server shipped together

Good fit Use it for feature work involving implementation, tests, API code, schemas, manifests, or documentation.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/affaan-m/ecc/feature-development
About the project

ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.

affaan-m/ECC · 282,704 stars · on GitHub · ecc.tools

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.

Clone the repo
git clone --depth 1 https://github.com/affaan-m/ECC

Made for: Claude Code.

Or install ecc, the plugin that ships this one along with the rest of its 78 skills, 58 commands, 70 agents, 1 MCP server.

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-development

README.md
[![agentmods](https://agentmods.dev/badge/commands/affaan-m/ecc/feature-development/github.svg)](https://agentmods.dev/commands/affaan-m/ecc/feature-development)
Your own site
<a href="https://agentmods.dev/commands/affaan-m/ecc/feature-development"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/feature-development/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.

agentmods 80×15 button for feature-development

Your own site · 80×15
<a href="https://agentmods.dev/commands/affaan-m/ecc/feature-development"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/feature-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 193 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review
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.00012 $0.00193
Opus 5.5 $0.00005 $0.00077
Sonnet 5.5 $0.00002 $0.00039
Haiku 4.5 $0.00001 $0.00019

Measured 16d ago against content hash a6c67508638a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-development 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 16d 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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

.claude/commands/feature-development.md · 38 lines

What it actually says

/feature-development

Use this workflow when working on feature-development in ECC.

Goal

Standard feature implementation workflow

Common Files

  • manifests/*
  • schemas/*
  • **/*.test.*
  • **/api/**

Suggested Sequence

  1. Understand the current state and failure mode before editing.
  2. Make the smallest coherent change that satisfies the workflow goal.
  3. Run the most relevant verification for touched files.
  4. Summarize what changed and what still needs review.

Typical Commit Signals

  • Add feature implementation
  • Add tests for feature
  • Update documentation

Notes

  • Treat this as a scaffold, not a hard-coded script.
  • Update the command if the workflow evolves materially.
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. 16d ago Changed · -4 tokens per session a6c67508638a
  2. 1mo ago First seen · 38 lines · 16 tokens per session scan A 95787804d23d

Subscribe to this mod's changes

feature-development is a command published in the GitHub repository affaan-m/ECC (282,704 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 193 once invoked, about $0.0000 per session on Opus 5.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.