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/vibehat/claude-task-manager/structured-plangit clone --depth 1 https://github.com/vibehat/claude-task-managerWhat 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.00000 | $0.00488 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
structured-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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structured Planning Workflow
Use this command when you need Claude to plan a feature or refactor following a structured, compliance-focused approach.
Usage: /structured-plan [your detailed prompt here]
Template
📋 STEP 1: READ REQUIREMENTS Claude, read the rules in CLAUDE.md, then use sequential thinking and proceed to the next step.
STOP. Before reading further, confirm you understand:
- This is a code reuse and consolidation project
- Creating new files requires exhaustive justification
- Every suggestion must reference existing code
- Violations of these rules make your response invalid
CONTEXT: Previous developer was terminated for ignoring existing code and creating duplicates. You must prove you can work within existing architecture.
MANDATORY PROCESS:
- Start with "COMPLIANCE CONFIRMED: I will prioritize reuse over creation"
- Analyze existing code BEFORE suggesting anything new
- Reference specific files from the provided analysis
- Include validation checkpoints throughout your response
- End with compliance confirmation
RULES (violating ANY invalidates your response): ❌ No new files without exhaustive reuse analysis ❌ No rewrites when refactoring is possible ❌ No generic advice - provide specific implementations ❌ No ignoring existing codebase architecture ✅ Extend existing services and components ✅ Consolidate duplicate code ✅ Reference specific file paths ✅ Provide migration strategies
$ARGUMENTS
FINAL REMINDER: If you suggest creating new files, explain why existing files cannot be extended. If you recommend rewrites, justify why refactoring won't work.
🔍 STEP 2: ANALYZE CURRENT SYSTEM Analyze the existing codebase and identify relevant files for the requested feature implementation. Then proceed to Step 3.
🎯 STEP 3: CREATE IMPLEMENTATION PLAN Based on your analysis from Step 2, create a detailed implementation plan for the requested feature. Then proceed to Step 4.
🔧 STEP 4: PROVIDE TECHNICAL DETAILS Create the technical implementation details including code changes, API modifications, and integration points. Then proceed to Step 5.
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 · 60 lines · 0 tokens per session scan A 97ddfb7eb2bd
structured-plan 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 488 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
deploy_to_docker
Build Docker image and start/redeploy the MCP Task Orchestrator container, reusing the last-used config by default.
check_schema_version
Check the Flyway schema version of the SQLite database on a Docker volume.
auto
Intent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another…
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.