Borrowing it
Nothing to install: this file belongs to changoo89/claude-pilot. 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/changoo89/claude-pilot/main/.claude/skills/confirm-plan/SKILL.mdgit clone --depth 1 https://github.com/changoo89/claude-pilotWrote 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/changoo89/claude-pilot/confirm-plan)<a href="https://agentmods.dev/skills/changoo89/claude-pilot/confirm-plan"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/confirm-plan/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/skills/changoo89/claude-pilot/confirm-plan"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/confirm-plan.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.00030 | $0.01401 |
| Opus 5.5 | $0.00012 | $0.00560 |
| Sonnet 5.5 | $0.00006 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
confirm-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 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Confirm Plan (Plan Confirmation Workflow)
Purpose: Extract plan from conversation, create plan file, run auto-review with Interactive Recovery Target: Plan-Reviewer Agent confirming plans after
/00_plan
Quick Start
When to Use This Skill
- Confirm plan after
/00_plancompletes - Create plan file in
.pilot/plan/draft/ - Run auto-review with Interactive Recovery for BLOCKING findings
- Verify 100% requirements coverage
Quick Reference
# TaskList Pattern: TaskUpdate (analyzing → completed) + TaskCreate (confirming)
TaskUpdate "analyzing" "completed"
TaskCreate "confirming" "in_progress"
# Extract plan from conversation
PLAN_CONTENT=$(extract_from_conversation "$CONVERSATION")
# Generate plan file name
TS="$(date +%Y%m%d_%H%M%S)"
PLAN_FILE="$PROJECT_ROOT/.pilot/plan/draft/${TS}_{work_name}.md"
# Requirements verification (BLOCKING if incomplete)
verify_requirements_coverage "$PLAN_CONTENT"
# Auto-review with Interactive Recovery
invoke_plan-reviewer "$PLAN_FILE"
resolve_blocking_findings "$PLAN_FILE"
What This Skill Covers
In Scope
- Dual-source extraction: Load decisions from draft file + scan conversation
- Cross-check verification: Compare draft vs conversation, detect omissions
- Plan file creation with full template structure
- Requirements verification (100% coverage required)
- Conversation highlights extraction (code examples, diagrams)
- Auto-review with Interactive Recovery for BLOCKING findings
- GPT delegation for large plans (5+ SCs)
Out of Scope
- Plan creation →
/00_plancommand - Plan execution →
/02_executecommand - TDD methodology → @.claude/skills/tdd/SKILL.md
Core Philosophy
No Execution: Only creates plan file and reviews | Context-Driven: Extract from conversation | English Only: Plan MUST be in English | Strict Mode Default: BLOCKING → Interactive Recovery
Definition of Done
Functional Completion:
- All SC implemented
- All tests passing
- Coverage >= 80%
What ships with it
1 file 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.
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 · 163 lines · 30 tokens per session scan A eba5f5dba46b
confirm-plan is a skill published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 8mo ago), licensed MIT. It adds 30 tokens to every session and 1,401 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
docs-decisions
Work on Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance. Use for files under docs/, documentation workflows, or requests to record or update a docs decision. Do not use for SDK runtime changes unless docs are the…
buyer-job-intent-analysis
Recover source-bound buyer jobs, struggling moments, desired progress, forces, workarounds, information acts, journey states, criteria, constraints, roles, locales, and authentic language. Use on approved ICP hypotheses plus customer, search, review, forum, procurement, support, or public-market evidence before…
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
session-wrap
Use when wrapping up a session before ending. 4 parallel subagents detect doc updates, repeated patterns, learning points, and follow-ups, then a verifier deduplicates and presents choices. Triggers on /session-wrap, session wrap, session cleanup, end of session.