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-analyzegit 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-analyze)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/features-analyze"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/features-analyze.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.00015 | $0.00967 |
| Opus 5 | $0.00008 | $0.00483 |
| Sonnet 5 | $0.00003 | $0.00193 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
features:analyze 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 4d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command /feature-list:analyze
Analyze existing codebase and generate feature specifications.
Instructions
Step 1: Launch Codebase Analyzer
Use the Task tool to spawn the codebase-analyzer agent:
Analyze the codebase at {path} and extract:
1. Domain entities (models, tables)
2. API endpoints (routes, handlers)
3. Business services
4. External integrations
For each entity, identify:
- CRUD operations
- Business rules (validations, constraints)
- Relationships and dependencies
- Current implementation status
Step 2: Process Analysis Results
From the analyzer output, categorize findings:
Core Features (from models):
- Each major model → potential core feature
- Identify domain codes from model names
Workflow Features (from services):
- Multi-step processes
- Cross-entity operations
Integration Features (from clients/adapters):
- External API clients
- Third-party service connections
Step 3: Check Existing Features
Use Glob to find existing feature files:
docs/technical-requirements/features/*.md
Compare with analysis to identify:
- New features to create
- Existing features to update
- Obsolete features to flag
Step 4: Confirm with User
Use AskUserQuestion to confirm the proposed features:
## Proposed Features
Based on codebase analysis, I found these features:
### Core (entities)
- [ ] `core-01-user` — User model with authentication
- [ ] `core-02-product` — Product catalog
### Workflow (processes)
- [ ] `workflow-01-checkout` — Order creation flow
### Integration (external)
- [ ] `integration-01-email` — SendGrid integration
Should I generate these feature specifications?
Step 5: Generate Feature Files
For each confirmed feature:
-
Determine next number for phase:
Glob: docs/technical-requirements/features/{phase}-*.md -
Generate feature file using template from SKILL.md
-
Extract business rules from code:
- Model validations → BR-XXX rules
- Unique constraints → BR-XXX rules
- Required fields → BR-XXX rules
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.
- 4d ago First seen · 174 lines · 15 tokens per session scan A 87c107119f4b
features:analyze is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 967 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
sync
Sync the audit manifest with Azure DevOps work items — set the connector up for the first time (connect: verify the transport, report which auth path is in effect, prove access read-only, detect the board's process), push manifest bugs/tasks/phases to ADO (board states, sprint stamp, Remaining Work, comments), pull…
init
Multi-agent codebase audit that GENERATES the audit manifest (phases/tasks) at manifestPath. Interviews you for scope/goals, fans out parallel read-only explorers, synthesizes findings, then presents the proposed phases for approval BEFORE writing — approve to materialize, or park them as proposals for later…
task
Add a tracked task to the audit manifest — every answer is a flag, and the dialogue only covers what the caller did not pass — move one between phases, or cancel work that will not be done. add allocates the id, initializes all orchestrator fields, updates fileIndex, and revalidates; move renumbers a task into another…
panel
Audit pipeline: open / stop / check a local control-panel UI to visually manage .claude/audit.config.json and the manifest's composition levers (reviewSkill, per-task skills/models, buildCommands) — with live validation and discovery of the skills & agents available in this repo + globally. Ephemeral, on-demand; a…
doctor
Audit pipeline: diagnose the setup before it bites — interpreter the hooks will use, git root, config, manifest + shard integrity, which plan-gate tier is active, submodule conflicts, build runners, whether the skills the plan names would resolve from a clone or only here, whether hooks have ever fired and which copy…
status
Audit pipeline: print manifest status — phases, tasks, bugs, the ready-now list and what each pending task is waiting on; or, with --gate, turn that same state into a CI pass/fail verdict over conditions you pick with --fail-on. Read-only, no locks, no mutations.