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/close-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/close-plan)<a href="https://agentmods.dev/skills/changoo89/claude-pilot/close-plan"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/close-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.1 | $0.00028 | $0.01054 |
| Opus 5 | $0.00014 | $0.00527 |
| Sonnet 5 | $0.00006 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
close-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 7d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Close Plan (Plan Completion Workflow)
Purpose: Archive completed plans and create git commits with safe push retry logic Target: Coder Agent after implementing all Success Criteria
Quick Start
When to Use This Skill
- Finalize completed plans
- Archive plan to done/ folder
- Create git commit with Co-Authored-By attribution
- Push to remote with retry logic
Quick Reference
# Full workflow
/03_close [RUN_ID|plan_path] [no-commit] [no-push] [--force]
# Steps: Load+Verify+TODO Gate → Evidence Verify → Docs Sync+Verify → Move+Git → Worktree Merge
Execution Directive
CRITICAL: NEVER skip any step - agent MUST verify execution of each step before proceeding to the next. All steps MUST execute in order. Do NOT pause between steps.
Agent Teams Delegation Pattern
Team Lead operates in delegate mode (coordinates only, never implements):
- Step 1 TODO analysis: Spawn teammate for TODO verification
- Step 2 evidence verification: Spawn teammate for test execution
- Step 3 docs sync: Spawn teammate for documentation updates (conditional)
MANDATORY teammate delegation:
- TODO gate resolution (role: validator)
- Evidence verification (role: validator)
- Documentation sync (role: documenter, conditional)
TRIVIAL EXCEPTIONS (no delegation needed):
- Argument parsing, file existence check, timestamp/directory creation, git commit formatting
WHY: Agent Teams native isolation provides automatic context protection
Execution Steps (Summary)
Step 0: Mandatory Oracle Consultation (NEW)
- Purpose: Pre-close quality verification
- GPT Role: QA Expert - Completion quality assessment
- Pattern: mandatory_oracle_consultation before proceeding
- Graceful Fallback: Continue if Codex CLI unavailable
Step 1: Load Plan + Verify SCs + TODO Gate
- Find active plan with absolute path detection
- Parse arguments (plan_path, no-commit, no-push, force)
- Check for incomplete Success Criteria
- TODO Completion Check (BLOCKING): Count unchecked
- [ ]items- Delegate to validator agent for TODO analysis and resolution attempt
- Exit if validator cannot resolve (unless --force flag)
- Full implementation: @REFERENCE.md - TODO Completion Gate
- TaskList Verification: Verify all tasks completed via TaskList tool
- Exit if no plan or SCs incomplete
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.
- 7d ago First seen · 124 lines · 28 tokens per session scan A 5390178c6292
close-plan is a skill published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 1,054 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 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.
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.
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.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.