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 skills/ronronner02/codepilot-agent/spec-plannpx skills add ronronner02/codepilot-agent --skill spec-plangit clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/skills/ronronner02/codepilot-agent/spec-plan)<a href="https://agentmods.dev/skills/ronronner02/codepilot-agent/spec-plan"><img src="https://agentmods.dev/badge/skills/ronronner02/codepilot-agent/spec-plan.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.00086 | $0.24042 |
| Opus 5 | $0.00043 | $0.12021 |
| Sonnet 5 | $0.00017 | $0.04808 |
| Haiku 4.5 | $0.00009 | $0.02404 |
Grade A, and why
spec-plan 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.
How it starts
The opening of the file, as written. The whole thing — 865 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Technical Plan
Note: Use the current date from the active host context. Use this when weighting external sources and dating artifacts.
spec-brainstorm defines WHAT to build by creating a requirements-only unified plan. spec-plan enriches that same artifact with HOW to build it. spec-work executes implementation-ready plans. A prior brainstorm is useful context but never required — spec-plan works from any input: a requirements-only unified plan, a legacy requirements doc, a bug report, a feature idea, or a rough description.
When directly invoked, always plan. Never classify a direct invocation as "not a planning task" and abandon the workflow. If the input is unclear, ask clarifying questions or use the planning bootstrap (Phase 0.4) to establish enough context — but always stay in the planning workflow. Here, "always plan" means entering and remaining in planning evaluation; entering planning evaluation does not promise an implementation-ready output. A blocked checkpoint or producer handoff is a valid outcome while product blockers remain.
This workflow produces a durable implementation plan. It does not implement code, run tests, or learn from execution-time results. If the answer depends on changing code and seeing what happens, that belongs in spec-work, not here.
Workflow Contract Summary
- Input: A requirements-only unified plan, legacy requirements, a bug or feature description, an existing plan, or an explicit answer-seeking objective.
- Output: An implementation-ready unified plan, the corresponding non-code or answer-seeking artifact, or a blocked checkpoint / producer handoff that preserves unresolved product questions.
- Hard exits: While WHAT is unsettled, the target repo or source owner is unclear, a load-bearing architecture or acceptance decision is unconfirmed, artifact metadata is invalid, or the user has not selected the owning handoff, do not modify the artifact to promote it to
implementation-ready, generate Implementation Units or an implementation handoff, or enter implementation. - Authority: The Product Contract owns WHAT; current source and evidence constrain HOW; the LLM makes architecture judgments while scripts only prepare facts. Planning does not authorize code mutation, tests, commits, or landing.
- Consumers:
spec-write-tasks,spec-work,spec-doc-review, human reviewers, and caller-owned pipelines.
What ships with it
29 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/agents/agent-native-planning-strategist.md 4.0 KB
- references/agents/architecture-strategist.md 4.7 KB
- references/agents/best-practices-researcher.md 7.0 KB
- references/agents/data-integrity-guardian.md 3.2 KB
- references/agents/data-migration-reviewer.md 5.7 KB
- references/agents/deployment-verification-agent.md 5.5 KB
- references/agents/framework-docs-researcher.md 5.5 KB
- references/agents/git-history-analyzer.md 2.8 KB
- references/agents/learnings-researcher.md 16 KB
- references/agents/pattern-recognition-specialist.md 4.6 KB
- references/agents/performance-oracle.md 4.5 KB
- references/agents/repo-research-analyst.md 15 KB
- references/agents/security-sentinel.md 4.0 KB
- references/agents/slack-researcher.md 10 KB
- references/agents/spec-flow-analyzer.md 4.7 KB
- references/agents/web-researcher.md 8.9 KB
- references/approach-altitude.md 7.0 KB
- references/deepening-workflow.md 22 KB
- references/frontend-engineering-lens.md 4.9 KB
- references/high-risk-plan-lens.md 7.6 KB
- references/html-rendering.md 34 KB
- references/interface-and-evolution-lens.md 6.0 KB
- references/markdown-rendering.md 10 KB
- references/plan-handoff.md 22 KB
- references/plan-sections.md 25 KB
- references/planning-evidence-boundaries.md 7.9 KB
- references/settled-decisions.md 4.8 KB
- references/synthesis-summary.md 41 KB
- references/universal-planning.md 15 KB
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 · 865 lines · 86 tokens per session scan A 86c71fa9c2ee
spec-plan is a skill published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 24,042 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
generate-ai-rules
Generate AI assistant configuration files for a repository — CLAUDE.md, AGENTS.md, and Cursor rules (.cursor/rules/.mdc) — from codebase analysis. Use whenever the user wants to create or update CLAUDE.md, AGENTS.md, agent rules, Cursor rules, AI coding assistant configuration, or "onboard AI tools" to a project, even…
generate-readme
Generate or refresh a comprehensive, professional README.md for a repository, with architecture overview, mermaid and optional C4 diagrams, repository structure, dependencies, and API documentation. Use whenever the user asks to create, write, update, improve, or regenerate a README, project documentation, or a…
analyze-codebase
Run a multi-agent deep analysis of a codebase, producing AI-readable analysis documents in .ai/docs/ covering structure, dependencies, data flow, request flow, and APIs. Use whenever the user asks to analyze a repository, generate codebase analysis, understand an unfamiliar codebase in depth, or before generating…
deploy-vercel-render
Deploy vpeetla-ai demos: Vercel static/Next.js frontends, Render FastAPI backends, env vars, free tier gotchas. Use when shipping demos, fixing deploy failures, or adding render.yaml / vercel.json.
langgraph-orchestration
Build or modify LangGraph StateGraph agents in vpeetla-ai repos: typed state, nodes, conditional edges, MemorySaver, interruptbefore HITL. Use when adding orchestrators, coding loops, or multi-agent graphs.
aegis-gateway
Integrate AegisAI gateway before tool side effects (notify, publish, deploy). Use when adding Slack/Telegram/WhatsApp notify, content publish, or any irreversible external action in VAP, AegisLoop, or ai-content-factory.