Borrowing it
Nothing to install: this file belongs to rhyanvargas/agentic-development-starter-kit. 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/rhyanvargas/agentic-development-starter-kit/main/.cursor/commands/plan-impl.mdgit clone --depth 1 https://github.com/rhyanvargas/agentic-development-starter-kitWrote 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/rhyanvargas/agentic-development-starter-kit/plan-impl)<a href="https://agentmods.dev/commands/rhyanvargas/agentic-development-starter-kit/plan-impl"><img src="https://agentmods.dev/badge/commands/rhyanvargas/agentic-development-starter-kit/plan-impl/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rhyanvargas/agentic-development-starter-kit/plan-impl"><img src="https://agentmods.dev/badge/commands/rhyanvargas/agentic-development-starter-kit/plan-impl.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00461 |
| Opus 5.5 | $0.00000 | $0.00184 |
| Sonnet 5.5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
plan-impl 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 2mo 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.
What it actually says
/plan-impl
Create an implementation plan from a specification.
Skill
Read and follow skills/spec-driven-workflow. Resolve paths with references/artifact-homes.md. For Cursor plan files, follow references/cursor-adapter.md (YAML todos required). When the engineering-methods pack is installed, use upstream writing-plans for granular task style — see docs/engineering-methods.md. Before planning Medium+, run or confirm the cross-requirement pass in references/analyze-requirements.md.
Usage
/plan-impl path/to/spec.md
Behavior
- Read the spec; if open questions or unconfirmed assumptions remain, resolve those before planning.
- Analyze (Medium+): cross-check REQs for conflicts, ambiguity, and gaps (
analyze-requirements.md). Update the living spec if findings change REQs. If a plan already exists and REQs changed, treat this as a resync (replace stale todos). - Break work into ordered, verifiable tasks (files, tests, risks). Prefer tasks that map to
REQ-XXXand stay within a focused file set. Prefer splitting build from verify/review so QA can run in parallel with the next slice. For bugfix specs, map tasks/tests to both FIX and KEEP (Unchanged) items. - Tracer gate (Large, and Medium when architecture/integration is ambiguous): include a thin vertical slice + one verify before multi-phase implement, or “N/A — architecture proven” with justification — see skill /
problem-size-guide.md. - Resolve the plan path via the skill. As a Cursor
/command, default to.cursor/plans/{feature-name}.plan.mdunless the project already usesdocs/plans/or the user overrides the path. - Write the plan with trackable todos (Cursor: non-empty frontmatter
todos; never body-only REQ tables with empty Plan UI todos). - Suggest
/implement-speconly after the user approves the plan (medium+).
Keep this command thin — planning depth lives in the skill / recommended upstream.
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.
- 2mo ago First seen · 26 lines · 0 tokens per session scan A 1714032ca9da
plan-impl is a command published in the GitHub repository rhyanvargas/agentic-development-starter-kit (2 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 461 tokens. 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.
plan-impl compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| plan-implrhyanvargas/agentic-development-starter-kit | Command | 2 | 4d ago | Apache-2.0 | A | 0 | Claude Code, Cursor |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |