add-feature

add-feature is a command for GitHub Copilot from kunalsuri/ai-fication-kit. It costs 23 tokens per session (370 once invoked), scanned A, original, Apache-2.0.

A guided workflow for adding a software feature from a written specification through code, tests, review, and project records. A specification is a written description of what the feature should do.

In plain words
What is it for?
Use it to plan a feature, locate the relevant code, implement it, run the appropriate tests, update maps and work logs, and move its roadmap item to shipped.
Why use it?
It reduces guesswork and keeps the change small, tested, reviewed, and reflected in the repository's planning documents.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt. Also seen: reads .claude/ paths.

Good fit Use it to plan a feature, locate the relevant code, implement it, run the appropriate tests, update maps and work logs, and move its roadmap item to shipped.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kunalsuri/ai-fication-kit/add-feature
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/kunalsuri/ai-fication-kit

Made for: GitHub Copilot.

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 add-feature

README.md
[![agentmods](https://agentmods.dev/badge/commands/kunalsuri/ai-fication-kit/add-feature/github.svg)](https://agentmods.dev/commands/kunalsuri/ai-fication-kit/add-feature)
Your own site
<a href="https://agentmods.dev/commands/kunalsuri/ai-fication-kit/add-feature"><img src="https://agentmods.dev/badge/commands/kunalsuri/ai-fication-kit/add-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.

agentmods 80×15 button for add-feature

Your own site · 80×15
<a href="https://agentmods.dev/commands/kunalsuri/ai-fication-kit/add-feature"><img src="https://agentmods.dev/badge/commands/kunalsuri/ai-fication-kit/add-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 370 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.
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.00023 $0.00370
Opus 5.5 $0.00009 $0.00148
Sonnet 5.5 $0.00005 $0.00074
Haiku 4.5 $0.00002 $0.00037

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

Security

Grade A, and why

add-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 28d 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.

.github/prompts/add-feature.prompt.md · 26 lines

What it actually says

Implement the requested feature following the add-feature skill contract (VS Code auto-discovers it from .claude/skills/add-feature/ or .agents/skills/add-feature/ in this repo). Summary of the contract:

  1. Spec first. If no spec exists in ai/lab/specs/, draft one from the template and get the user's OK before writing code.
  2. Locate via the maps. MODULE_MAP → FEATURE_MAP/CATALOG → WORKLOG history (was this area just changed?) → open only what's needed.
  3. Respect Stability. Never modify frozen or ? files without explicit human approval in this conversation.
  4. Build surgically. Smallest diff that satisfies the spec; match conventions and license headers.
  5. Verify. Run the suite(s) matching the change. Failing or unrun tests ⇒ not done.
  6. Update knowledge. FEATURE_MAP entry, catalog amendment, MODULE_MAP if layout changed — all tagged [inferred] for the human to verify.
  7. Review & record. Request /review-change on the diff (fresh context), then append the work's row to ai/lab/WORKLOG.md linking spec, review, and commits, and move the feature's ai/lab/ROADMAP.md row from Planned to Shipped — cross-linking the spec, the WORKLOG row, and the PR by feature ID.
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. 28d ago First seen · 26 lines · 23 tokens per session scan A 4347b476d677

Subscribe to this mod's changes

add-feature is a command published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 370 once invoked, about $0.0001 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-09-18.