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-designgit clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWhat 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.00014 | $0.01450 |
| Opus 5 | $0.00007 | $0.00725 |
| Sonnet 5 | $0.00003 | $0.00290 |
| Haiku 4.5 | $0.00001 | $0.00145 |
Grade A, and why
features:design 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command /feature-list:design
Interactive feature design session for new or greenfield projects.
Instructions
Step 1: Understand Project Context
Use AskUserQuestion to gather initial context:
questions:
- question: "What type of application are you building?"
header: "App Type"
options:
- label: "E-commerce"
description: "Online store with products, cart, checkout"
- label: "SaaS Platform"
description: "Multi-tenant application with subscriptions"
- label: "API Service"
description: "Backend API for mobile/web clients"
- label: "Internal Tool"
description: "Admin panel or back-office system"
Step 2: Identify User Roles
questions:
- question: "What user roles will your application have?"
header: "User Roles"
multiSelect: true
options:
- label: "Anonymous User"
description: "Unauthenticated visitors"
- label: "Registered User"
description: "Authenticated regular users"
- label: "Admin"
description: "System administrators"
- label: "Moderator"
description: "Content or user moderators"
Step 3: Define Core Entities
Based on project type, suggest core entities:
E-commerce:
- User, Product, Category, Cart, Order, Payment
SaaS:
- User, Organization, Team, Subscription, Feature
API Service:
- User, APIKey, RateLimit, Webhook
Ask user to confirm or modify:
questions:
- question: "Which core entities does your system need?"
header: "Entities"
multiSelect: true
options:
- label: "Users"
description: "User accounts and profiles"
- label: "Products"
description: "Items for sale or display"
- label: "Orders"
description: "Purchase transactions"
- label: "Organizations"
description: "Multi-tenant companies/teams"
Step 4: Define Key Workflows
questions:
- question: "What are the main workflows in your application?"
header: "Workflows"
multiSelect: true
options:
- label: "User Registration"
description: "Sign up, email verification, onboarding"
- label: "Purchase Flow"
description: "Cart → Checkout → Payment → Confirmation"
- label: "Content Publishing"
description: "Draft → Review → Publish"
- label: "Approval Process"
description: "Submit → Review → Approve/Reject"
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 · 252 lines · 14 tokens per session scan A c72e1cdb87b0
features:design is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,450 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
create-command
Create slash commands with brainstorming and best practices.
create-hook
Create hooks with brainstorming and security-first design.
improve-skills
Identify and implement skill improvements from execution logs and user evaluations.
validate-hook
Validate hooks for security, performance, and SDK compliance.
hooks-eval
Evaluate all hooks in a plugin for quality and compliance.
evaluate-skill
Manually evaluate a recent skill execution to record qualitative feedback.