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/parse-prdgit 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.00236 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
parse-prd 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
100% identical to parse-prd — 5 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
Parse a PRD document to generate tasks.
Arguments: $ARGUMENTS (PRD file path)
Intelligent PRD Parsing
Analyzes your requirements document and generates a complete task breakdown.
Execution
task-master parse-prd --input=$ARGUMENTS
Parsing Process
-
Document Analysis
- Extract key requirements
- Identify technical components
- Detect dependencies
- Estimate complexity
-
Task Generation
- Create 10-15 tasks by default
- Include implementation tasks
- Add testing tasks
- Include documentation tasks
- Set logical dependencies
-
Smart Enhancements
- Group related functionality
- Set appropriate priorities
- Add acceptance criteria
- Include test strategies
Options
Parse arguments for modifiers:
- Number after filename →
--num-tasks research→ Use research modecomprehensive→ Generate more tasks
Post-Generation
After parsing:
- Display task summary
- Show dependency graph
- Suggest task expansion for complex items
- Recommend sprint planning
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 · 54 lines · 0 tokens per session scan A 49bcd20f72e0
parse-prd 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 236 tokens. A static security scan graded it A with 0 findings. It is 100% identical to parse-prd, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
pm-arch
Scan project structure and generate Mermaid architecture diagrams + flowcharts under .pm/architecture/.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
pm-status
Show governance health, wizard next step, all open blocking/high todos, and pending review count. Primary daily entry.
pm-charter
Create, import, discover, approve, or skip project charter. No-arg form is an interactive wizard.
pm-check
Diagnose .pm/ health (missing files, broken audit, stale map, unconfirmed PRD) and repair or increment without overwriting confirmed content.