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/alexgvozden/claude-plugin/plan-featuregit clone --depth 1 https://github.com/alexgvozden/claude-pluginWrote 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/alexgvozden/claude-plugin/plan-feature)<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/plan-feature"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/plan-feature.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.00016 | $0.01168 |
| Opus 5 | $0.00008 | $0.00584 |
| Sonnet 5 | $0.00003 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
plan-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 5d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: PLANNING ONLY - NO CODE IMPLEMENTATION
This command is exclusively for PLANNING features. Do NOT:
- Write any code
- Create or modify components
- Install dependencies
- Run any bash commands
- Make any changes to the codebase
ONLY:
- Read existing files to understand context
- Create or update planning documentation in the planning/ folder
- Ask clarifying questions about requirements
You are tasked with planning a feature for the Database Analysis application following the workflow outlined in CLAUDE.md.
Instructions
-
Understand the Feature Request:
- If a planning file path is provided (e.g., planning/feature-name.md), read it to understand the existing plan
- If no file is provided or it doesn't exist, this is a new feature - understand requirements from the user's description
- Identify the feature scope, goals, and success criteria
-
Follow CLAUDE.md Planning Workflow:
- Review CLAUDE.md for project structure, tech stack, and guidelines
- Ensure the plan respects:
- Next.js and React best practices
- Existing database patterns (use getPool() from @/lib/db-connections)
- Tailwind CSS styling conventions
- Existing UI component patterns (Shadcn/UI)
- CamelCase naming for database tables
- API endpoint documentation requirements
-
Create Comprehensive Plan:
Structure the plan with these sections:
Feature: [Feature Name]
Overview
- Brief description of the feature
- Business value and goals
- Target users
Requirements
- Functional requirements (numbered list)
- Non-functional requirements (performance, security, etc.)
Technical Design
Database Changes
- Schema modifications needed
- New tables (use CamelCase naming)
- Migrations required
- Example SQL if applicable
API Endpoints
- List all new/modified endpoints
- Request/response schemas
- Authentication requirements
- Error handling approach
- API Documentation: Each feature should have a Postman collection in
docs/api/- Create new Postman collection for the feature (e.g.,
docs/api/feature-name.postman_collection.json) - Include all endpoints with examples
- Document request parameters, headers, and body
- Include sample responses (success and error cases)
- Add environment variables if needed
- Create new Postman collection for the feature (e.g.,
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.
- 5d ago First seen · 153 lines · 16 tokens per session scan A 653a147ffc45
plan-feature is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 1,168 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.