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 commands/shakestzd/contextune/ctx-plangit clone --depth 1 https://github.com/shakestzd/contextuneWrote 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/shakestzd/contextune/ctx-plan)<a href="https://agentmods.dev/commands/shakestzd/contextune/ctx-plan"><img src="https://agentmods.dev/badge/commands/shakestzd/contextune/ctx-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.00016 | $0.03664 |
| Opus 5 | $0.00008 | $0.01832 |
| Sonnet 5 | $0.00003 | $0.00733 |
| Haiku 4.5 | $0.00002 | $0.00366 |
Grade A, and why
ctx: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 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.
How it starts
The opening of the file, as written. The whole thing — 609 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Plan - Create Modular YAML Development Plan
You are executing the parallel planning workflow. Your task is to analyze the conversation history and create a modular YAML plan for parallel development.
Key Innovation: Each task is a separate YAML file. No more monolithic markdown files!
Benefits:
- ✅ 95% fewer tokens for updates (edit one task file vs entire plan)
- ✅ Add/remove tasks without touching existing content
- ✅ Reorder tasks with simple array edits
- ✅ Better version control (smaller, focused diffs)
- ✅ No time/duration estimates (use tokens and priority instead)
- ✅ Priority + dependencies (what actually matters for execution)
DRY Strategy Note:
- Plans use extraction-optimized output format (visibility + iteration)
- NO Write tool during planning (user sees full plan in conversation)
/ctx:executeextracts plan automatically when needed- SessionEnd hook as backup (extracts at session end)
- Result: Modular files created automatically, zero manual work
This command is part of the Contextune plugin and can be triggered via natural language or explicitly with /contextune:parallel:plan.
Step 1: Analyze Conversation and Requirements
Review the conversation history to identify:
- What features/tasks the user wants to implement
- Which tasks are independent (can run in parallel)
- Which tasks have dependencies (must run sequentially)
- Potential shared resources or conflict zones
Use the following criteria to classify tasks:
Independent Tasks (Parallel-Safe):
- Touch different files
- Different modules/features
- No shared state
- Can complete in any order
Dependent Tasks (Sequential):
- Task B needs Task A's output
- Database migrations
- Shared file modifications
- Order matters
Conflict Risks:
- Same file edits
- Shared configuration
- Database schema changes
- API contract changes
Step 2: Parallel Research (NEW! - Grounded Research)
IMPORTANT: Before planning, do comprehensive research using 5 parallel agents!
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.
- 3d ago First seen · 609 lines · 16 tokens per session scan A 6d25de35d83e
ctx:plan is a command published in the GitHub repository shakestzd/contextune (5 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 3,664 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-31.
Other commands, from other repositories
security-review
CWE 기반 보안 검토 + STRIDE 위협 모델링 (v6 - effort:max 강제).
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
version
Display current guide and Claude Code versions.
docs-review
Phase 4 of documenting-projects: Quality gate with 8 measurable criteria and iteration. Triggers: '/docs-review', invoked by documenting-projects orchestrator.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
memcord-save-progress
Auto-summarize and save conversation progress.