CONTEXT

A set of slash commands for a SPEC-First development workflow, where the plan and requirements are written before coding begins.

In plain words
What is it for?
Use it to configure tools, create and confirm plans, execute work with TDD, fix bugs, clean up code, review changes, update documentation, and release versions.
Why use it?
It gives coding tasks a defined sequence for planning, checking requirements, implementation, testing, review, documentation, and release.

Command for Claude Code

Part of the claude-pilot plugin — 32 skills, 11 commands, 14 agents, 2 MCP servers shipped together

Install

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.

agentmods
npx agentmods add commands/changoo89/claude-pilot/context
Clone the repo
git clone --depth 1 https://github.com/changoo89/claude-pilot

Made for: Claude Code.

Or install claude-pilot, the plugin that ships this one along with the rest of its 32 skills, 11 commands, 14 agents, 2 MCP servers.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 876 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00876
Opus 5 $0.00000 $0.00438
Sonnet 5 $0.00000 $0.00175
Haiku 4.5 $0.00000 $0.00088

Measured 3d ago against content hash fdbecc4d9ce8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

.claude/commands/CONTEXT.md · 107 lines

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


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

Read the full file on GitHub · 107 lines

Changes

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.

  1. 3d ago First seen · 107 lines · 0 tokens per session scan A fdbecc4d9ce8

Subscribe to this mod's changes

CONTEXT is a command published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 6mo 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.