Borrowing it
Nothing to install: this file belongs to solanabr/solana-glossary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/solanabr/solana-glossary/main/.claude/commands/plan-feature.mdgit clone --depth 1 https://github.com/solanabr/solana-glossaryWrote 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/solanabr/solana-glossary/plan-feature)<a href="https://agentmods.dev/commands/solanabr/solana-glossary/plan-feature"><img src="https://agentmods.dev/badge/commands/solanabr/solana-glossary/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.1 | $0.00010 | $0.01958 |
| Opus 5 | $0.00005 | $0.00979 |
| Sonnet 5 | $0.00002 | $0.00392 |
| Haiku 4.5 | $0.00001 | $0.00196 |
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 7d 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.
This is a copy
100% identical to plan-feature — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a detailed implementation plan for a Solana blockchain feature.
Feature Description
$ARGUMENTS
Planning Framework
1. Feature Analysis
Break down the feature into:
User Stories
- As a [user type], I want to [action] so that [benefit]
Technical Requirements
- On-chain components (programs, accounts)
- Off-chain components (clients, indexers)
- Integration points
Dependencies
- External programs (Token, Metaplex, etc.)
- SDKs and libraries
- Infrastructure (RPC, indexer)
Edge Cases
- Error conditions
- Boundary values
- Concurrent access
Success Criteria
- Functional requirements met
- Security requirements met
- Performance targets met
2. Architecture Design
On-Chain Architecture
┌─────────────────────────────────────────────────┐
│ Your Program │
├─────────────────────────────────────────────────┤
│ Instructions │ Accounts │ Events │
│ - initialize │ - UserAccount │ - Init │
│ - action │ - StateAccount │ - Action│
│ - close │ - VaultPDA │ - Close │
└─────────────────────────────────────────────────┘
│ │
▼ ▼
┌─────────────────┐ ┌─────────────────┐
│ Token Program │ │ System Program │
└─────────────────┘ └─────────────────┘
Client Architecture
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Frontend │────▶│ SDK/Client │────▶│ RPC │
│ (React/ │ │ (@solana/ │ │ (Helius/ │
│ Unity) │ │ kit) │ │ Triton) │
└──────────────┘ └──────────────┘ └──────────────┘
Data Flow
User Action → Frontend → Transaction Build → Sign → Send → Confirm → Update UI
3. Account Design
For each account type:
### [AccountName]
**Purpose:** [What this account stores]
**Seeds (if PDA):** `["prefix", key1, key2]`
**Size:** [Calculate exact bytes]
| Field | Type | Size | Description |
|-------|------|------|-------------|
| discriminator | [u8; 8] | 8 | Anchor discriminator |
| field1 | Pubkey | 32 | Description |
| field2 | u64 | 8 | Description |
| **Total** | | **X** | + rent exempt |
**Rent:** ~X.XXX SOL
**Lifecycle:**
1. Created by: [instruction]
2. Modified by: [instructions]
3. Closed by: [instruction]
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.
- 7d ago First seen · 348 lines · 10 tokens per session scan A c9f93026166b
plan-feature is a command published in the GitHub repository solanabr/solana-glossary (19 stars, last pushed 27d ago), licensed MIT. It adds 10 tokens to every session and 1,958 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to plan-feature, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
question
Read-only code Q&A. Spawns the code-explorer subagent (Haiku-class) to grep, glob, and read excerpts of the codebase, then synthesizes a cited answer with file:line citations. No plan, no gates, no implementation. Fast. Triggers: "where is X defined", "what calls Y", "how does Z work", "find references to", "explain…
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.