Borrowing it
Nothing to install: this file belongs to vibehat/claude-task-manager. 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/vibehat/claude-task-manager/master/.claude/commands/plan-with-context.mdgit clone --depth 1 https://github.com/vibehat/claude-task-managerWrote 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/vibehat/claude-task-manager/plan-with-context)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/plan-with-context"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/plan-with-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/vibehat/claude-task-manager/plan-with-context"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/plan-with-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.00298 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
plan-with-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 1mo 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.
What it actually says
Plan with Context - Context-Aware Implementation Planning
Use this command after analysis to create implementation plans that respect existing architecture.
Usage: /plan-with-context [implementation request]
Context-Driven Planning
PLANNING REQUEST: $ARGUMENTS
PREREQUISITE CHECK:
- ✓ Codebase analysis completed
- ✓ Existing patterns identified
- ✓ Reuse opportunities evaluated
- ✓ Architecture constraints understood
IMPLEMENTATION STRATEGY:
1. EXISTING CODE INTEGRATION
- Files to extend: [list with specific paths]
- Components to reuse: [list with locations]
- Patterns to follow: [document existing patterns]
- Utilities to leverage: [identify reusable functions]
2. MINIMAL ADDITION APPROACH
- What truly needs to be new: [justify each new component]
- How new code integrates: [specific integration points]
- Consistency with existing style: [follow established conventions]
3. TECHNICAL IMPLEMENTATION
- File modifications: [specific files and changes]
- New files (if justified): [with exhaustive reasoning]
- API changes: [minimal necessary changes]
- Testing strategy: [leverage existing test patterns]
4. VALIDATION CHECKPOINTS
- Architecture consistency maintained
- Existing code reused maximally
- New additions minimized and justified
- Integration points clearly defined
COMPLIANCE CONFIRMATION: This plan prioritizes reuse and follows existing architecture patterns.
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.
- 1mo ago First seen · 48 lines · 0 tokens per session scan A f351ff285890
plan-with-context is a command published in the GitHub repository vibehat/claude-task-manager (21 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 298 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
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
discuss
A command that interviews you in five phases and saves a detailed description of a proposed feature or change. EARS is a structured way to write requirements so they can be checked clearly.
sdd
A command that creates three connected planning files for a software feature: requirements, design, and tasks.
traceability-gen
A command that rebuilds a Markdown table linking requirements to project plans and tests. It reads requirement files, plan files, and test markers, then records what is planned or covered.
web-inspect
Browser-based investigation using playwright-cli — open pages, inspect elements, check console errors, capture screenshots. Headed mode by default.
aic-help
Show AIContext quickstart guide with setup, workflows, and best practices.