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/rhyanvargas/agentic-development-starter-kit/plan-implgit clone --depth 1 https://github.com/rhyanvargas/agentic-development-starter-kitWhat 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.00000 | $0.00461 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 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 yesterday.
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.
- yesterday 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 8d 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.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.