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.
npx agentmods add commands/ruslan-korneev/claude-plugins/features-statusgit clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWrote 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/ruslan-korneev/claude-plugins/features-status)<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>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 | $0.00012 | $0.01294 |
| Opus 5 | $0.00006 | $0.00647 |
| Sonnet 5 | $0.00002 | $0.00259 |
| Haiku 4.5 | $0.00001 | $0.00129 |
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.
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:
idtitlestatus(draft | in_progress | completed)phasepriority
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)
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.
- 3d ago First seen · 219 lines · 12 tokens per session scan A 579bb12bd1b1
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.
Other commands, from other repositories
contact-upsert
Create or update a contact, optionally assign to groups.
sheet-report
Analyze a Numbers or Excel file and generate a report with charts.
csv-to-numbers
Convert a CSV into a formatted Numbers workbook.
excel-to-numbers
Convert an Excel workbook to Numbers.
meeting-start
Detect the current meeting, start a Voice Memo recording, and mark attendance.
numbers-to-excel
Convert a Numbers document to Excel.