features:status

features:status is a command for coding agents from ruslan-korneev/claude-plugins. It costs 12 tokens per session (1,294 once invoked), scanned A, original, MIT.

A command that reports how planned features are progressing, grouped by development phase. It reads feature documents and counts items marked draft, in progress, or completed.

In plain words
What is it for?
Use it to scan feature files, group them by phase and status, and calculate totals and completion percentages.
Why use it?
It provides a quick view of unfinished work and overall progress without opening every feature document. This makes it easier to see which phases need attention.

Command

Part of the tech-lead plugin — 14 commands, 9 agents 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 commands/ruslan-korneev/claude-plugins/features-status
Clone the repo
git clone --depth 1 https://github.com/ruslan-korneev/claude-plugins

Or install tech-lead, the plugin that ships this one along with the rest of its 14 commands, 9 agents.

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 features:status

README.md
[![agentmods](https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/features-status.svg)](https://agentmods.dev/commands/ruslan-korneev/claude-plugins/features-status)
Your own site
<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/features-status"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/features-status.svg" alt="Measured on agentmods" 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 1,294 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 $0.00012 $0.01294
Opus 5 $0.00006 $0.00647
Sonnet 5 $0.00002 $0.00259
Haiku 4.5 $0.00001 $0.00129

Measured 3d ago against content hash 579bb12bd1b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

features:status 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 3d 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.

plugins/tech-lead/commands/features-status.md · 219 lines

How it starts

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

Command /feature-list:status

Display the implementation status of all features grouped by phase.

Instructions

Step 1: Find All Feature Files

Use Glob to find feature files:

docs/technical-requirements/features/*.md

Exclude README.md and 00-template.md.

Step 2: Parse Each Feature

For each file, extract from YAML frontmatter:

  • id
  • title
  • status (draft | in_progress | completed)
  • phase
  • priority

Step 3: Calculate Statistics

Group features by phase and status:

stats = {
    "core": {"completed": 0, "in_progress": 0, "draft": 0},
    "workflow": {"completed": 0, "in_progress": 0, "draft": 0},
    # ...
}

for feature in features:
    stats[feature.phase][feature.status] += 1

Calculate totals and percentages:

total = len(features)
completed = sum(1 for f in features if f.status == "completed")
completion_rate = (completed / total * 100) if total > 0 else 0

Step 4: Generate Report

Summary Table
## Feature Implementation Status

### Summary

| Phase | Total | ✅ Completed | 🔄 In Progress | 📝 Draft | Progress |
|-------|-------|--------------|----------------|----------|----------|
| Core | 4 | 2 | 1 | 1 | 50% |
| Workflow | 2 | 0 | 1 | 1 | 0% |
| Integration | 3 | 3 | 0 | 0 | 100% |
| **Total** | **9** | **5** | **2** | **2** | **56%** |
Detailed by Phase
### Core Features

| ID | Feature | Status | Priority |
|----|---------|--------|----------|
| core-01 | User Management | ✅ Completed | Critical |
| core-02 | Product Catalog | ✅ Completed | High |
| core-03 | Inventory | 🔄 In Progress | Medium |
| core-04 | Categories | 📝 Draft | Low |

### Workflow Features

| ID | Feature | Status | Priority |
|----|---------|--------|----------|
| workflow-01 | Checkout | 🔄 In Progress | Critical |
| workflow-02 | Returns | 📝 Draft | Medium |
Progress Bar (ASCII)
### Overall Progress

[████████████░░░░░░░░] 56% (5/9 features completed)

Read the full file on GitHub · 219 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. 3d ago First seen · 219 lines · 12 tokens per session scan A 579bb12bd1b1

Subscribe to this mod's changes

features:status is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 1,294 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.