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/implement-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/implement-feature)<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/implement-feature"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/implement-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.00013 | $0.02664 |
| Opus 5 | $0.00006 | $0.01332 |
| Sonnet 5 | $0.00003 | $0.00533 |
| Haiku 4.5 | $0.00001 | $0.00266 |
Grade A, and why
implement-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 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: IMPLEMENTATION WITH STEP-BY-STEP EXECUTION
This command implements a feature based on a planning document, executing one logical step at a time with user review checkpoints.
Required Parameter
Planning Document Path: You MUST provide the path to the feature planning markdown file.
Example usage:
/implement-feature planning/my-feature.md
Instructions
1. Validate Planning Document
Read the planning document and verify:
- File exists at the provided path
- Contains
### Implementation Phaseswith clear phase breakdown and specific tasks - Has required sections: Overview, Requirements, Technical Design, Testing Strategy, Acceptance Criteria
If validation fails: Inform user what's missing and suggest running /plan-feature first. EXIT without proceeding.
2. Create Implementation Plan
If all validation passes, create a detailed implementation plan:
Extract Phases and Tasks Parse the ### Implementation Phases section Create a structured list of all phases and tasks Number tasks hierarchically (1.1, 1.2, 2.1, 2.2, etc.) Identify file paths for each task Note any dependencies between tasks Add Progress Tracker to Planning Document IMPORTANT: Update the planning document by adding a progress tracker table at the TOP of the file (right after the feature title, before Overview):
Feature: [Feature Name]
Implementation Progress
| Phase | Task | Status | Notes |
|---|---|---|---|
| Phase 1: [Name] | |||
| 1.1 | [Task description] | ⏸️ Pending | |
| 1.2 | [Task description] | ⏸️ Pending | |
| Phase 2: [Name] | |||
| 2.1 | [Task description] | ⏸️ Pending | |
| 2.2 | [Task description] | ⏸️ Pending | |
| Phase 3: [Name] | |||
| 3.1 | [Task description] | ⏸️ Pending |
Legend: ✅ Complete | 🔄 In Progress | ⏸️ Pending | ❌ Blocked
Overview
[Rest of original planning document content...] Present Implementation Plan to User Show the user a summary:
📋 Implementation Plan Created
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 · 368 lines · 13 tokens per session scan A 08e0da0901f2
implement-feature is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 2,664 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.