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/sakrut/ai-code-graph/expand-taskgit clone --depth 1 https://github.com/sakrut/ai-code-graphWhat 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.00258 |
| Opus 5 | $0.00000 | $0.00129 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
expand-task 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 yesterday.
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.
This is a copy
92% identical to expand-task — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Expand Task
Arguments: $ARGUMENTS Break down a complex task into subtasks.
Arguments: $ARGUMENTS (task ID)
Intelligent Task Expansion
Analyzes a task and creates detailed subtasks for better manageability.
Execution
task-master expand --id=$ARGUMENTS
Expansion Process
-
Task Analysis
- Review task complexity
- Identify components
- Detect technical challenges
- Estimate time requirements
-
Subtask Generation
- Create 3-7 subtasks typically
- Each subtask 1-4 hours
- Logical implementation order
- Clear acceptance criteria
-
Smart Breakdown
- Setup/configuration tasks
- Core implementation
- Testing components
- Integration steps
- Documentation updates
Enhanced Features
Based on task type:
- Feature: Setup → Implement → Test → Integrate
- Bug Fix: Reproduce → Diagnose → Fix → Verify
- Refactor: Analyze → Plan → Refactor → Validate
Post-Expansion
After expansion:
- Show subtask hierarchy
- Update time estimates
- Suggest implementation order
- Highlight critical path
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.
- yesterday First seen · 52 lines · 0 tokens per session scan A 8672900f2520
expand-task is a command published in the GitHub repository sakrut/ai-code-graph (3 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 258 tokens. A static security scan graded it A with 0 findings. It is 92% identical to expand-task, differing in 3 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.