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/asachs01/float-mcp/convert-task-to-subtaskgit clone --depth 1 https://github.com/asachs01/float-mcpWhat 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.00398 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
convert-task-to-subtask 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 2d 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.
This is a copy
100% identical to convert-task-to-subtask — 2 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
Convert an existing task into a subtask.
Arguments: $ARGUMENTS
Parse parent ID and task ID to convert.
Task Conversion
Converts an existing standalone task into a subtask of another task.
Argument Parsing
- "move task 8 under 5"
- "make 8 a subtask of 5"
- "nest 8 in 5"
- "5 8" → make task 8 a subtask of task 5
Execution
task-master add-subtask --parent=<parent-id> --task-id=<task-to-convert>
Pre-Conversion Checks
-
Validation
- Both tasks exist and are valid
- No circular parent relationships
- Task isn't already a subtask
- Logical hierarchy makes sense
-
Impact Analysis
- Dependencies that will be affected
- Tasks that depend on converting task
- Priority alignment needed
- Status compatibility
Conversion Process
- Change task ID from "8" to "5.1" (next available)
- Update all dependency references
- Inherit parent's context where appropriate
- Adjust priorities if needed
- Update time estimates
Smart Features
- Preserve task history
- Maintain dependencies
- Update all references
- Create conversion log
Example
/project:tm/add-subtask/from-task 5 8
→ Converting: Task #8 becomes subtask #5.1
→ Updated: 3 dependency references
→ Parent task #5 now has 1 subtask
→ Note: Subtask inherits parent's priority
Before: #8 "Implement validation" (standalone)
After: #5.1 "Implement validation" (subtask of #5)
Post-Conversion
- Show new task hierarchy
- List updated dependencies
- Verify project integrity
- Suggest related conversions
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.
- 2d ago First seen · 73 lines · 0 tokens per session scan A b5ea1145f83b
convert-task-to-subtask is a command published in the GitHub repository asachs01/float-mcp (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 398 tokens. A static security scan graded it A with 0 findings. It is 100% identical to convert-task-to-subtask, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
pm-init
Initialize local .pm governance; detect Spec Kit; if absent, analyze the repo and draft a PRD for user confirmation; after confirm/skip run a technical light scan.
pm-all
Full technical governance scan; rebuild .pm/dashboard. Default does not wait on draft PRD. Use --compare-baseline only after a confirmed PRD/charter.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-export
Export desensitized governance summary markdown for sharing or machine switch.
pm-outline
Generate detailed project outline and draft charter from user intent (empty/new projects).
pm-status
Show governance health, wizard next step, all open blocking/high todos, and pending review count. Primary daily entry.