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/commands/CONTEXT.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/commands/changoo89/claude-pilot/context)<a href="https://agentmods.dev/commands/changoo89/claude-pilot/context"><img src="https://agentmods.dev/badge/commands/changoo89/claude-pilot/context/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/changoo89/claude-pilot/context"><img src="https://agentmods.dev/badge/commands/changoo89/claude-pilot/context.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.00876 |
| Opus 5.5 | $0.00000 | $0.00350 |
| Sonnet 5.5 | $0.00000 | $0.00175 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
CONTEXT 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commands Context
Slash commands for SPEC-First development workflow.
Quick Reference
| Command | Purpose | Phase |
|---|---|---|
/setup |
Configure MCP servers | Setup |
/00_plan |
Create SPEC-First plan | Planning |
/01_confirm |
Confirm plan + gap detection | Planning |
/02_execute |
Execute with TDD + Ralph Loop | Execution |
/03_close |
Archive and commit | Completion |
/04_fix |
Rapid bug fix workflow | Rapid |
/05_cleanup |
Dead code cleanup | Maintenance |
/review |
Multi-angle code review | Quality |
/document |
Sync documentation | Maintenance |
/999_release |
Version bump + release | Release |
Workflow Sequence
User Request
↓
/00_plan (read-only exploration via planning-team)
↓
/01_confirm (requirements verification via plan-reviewer)
↓
/02_execute (TDD + Ralph Loop via execution-team)
↓
/03_close (archive + commit with validator/documenter)
↓
/review (anytime via review-team - optional)
Alternative: /04_fix for simple bugs
Agent Teams Architecture: All workflow commands leverage Agent Teams for parallel execution and direct teammate communication.
Phase Boundary Protection
Planning Phase Rules:
- CAN DO: Read, Search, Analyze, Discuss, Plan
- CANNOT DO: Edit files, Write files, Create code, Implement
Implementation Phase: Starts ONLY after /01_confirm → /02_execute
Related Skills
Each command delegates to appropriate skills:
- agent-teams: Agent Teams coordination patterns
- spec-driven-workflow: Plan creation with planning-team
- execute-plan: SC execution via execution-team (Team Lead spawns coder, frontend-engineer, backend-engineer teammates)
- confirm-plan: Plan verification via plan-reviewer teammate
- close-plan: Archive and commit with validator/documenter teammates
- parallel-subagents: Rewritten for Agent Teams (teammate spawn patterns)
- tdd: Test-driven development (used by coder teammates)
- ralph-loop: Autonomous iteration (used by coder teammates)
- git-master: Git operations
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 · 107 lines · 0 tokens per session scan A fdbecc4d9ce8
CONTEXT is a command published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 876 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-30.
Other commands, from other repositories
suggest-automation
A command that reviews recent Git commits and project instructions to find work patterns that happen repeatedly.
evolve
Cluster related instincts into skills, commands, or agents.
context-stats
Display context window usage and token statistics.
instinct-import
Import instincts from teammates, Skill Creator, or other sources.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
instinct-export
Export instincts for sharing with teammates or other projects.