Borrowing it
Nothing to install: this file belongs to TICnine/autotask-mcp. 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/TICnine/autotask-mcp/main/.claude/commands/tm/parse-prd/parse-prd-with-research.mdgit clone --depth 1 https://github.com/TICnine/autotask-mcpWrote 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/ticnine/autotask-mcp/parse-prd-with-research)<a href="https://agentmods.dev/commands/ticnine/autotask-mcp/parse-prd-with-research"><img src="https://agentmods.dev/badge/commands/ticnine/autotask-mcp/parse-prd-with-research.svg" alt="Measured on agentmods" 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.00215 |
| Opus 5 | $0.00000 | $0.00108 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
parse-prd-with-research 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 7d 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 parse-prd-with-research — 0 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 PRD with enhanced research mode for better task generation.
Arguments: $ARGUMENTS (PRD file path)
Research-Enhanced Parsing
Uses the research AI provider (typically Perplexity) for more comprehensive task generation with current best practices.
Execution
task-master parse-prd --input=$ARGUMENTS --research
Research Benefits
-
Current Best Practices
- Latest framework patterns
- Security considerations
- Performance optimizations
- Accessibility requirements
-
Technical Deep Dive
- Implementation approaches
- Library recommendations
- Architecture patterns
- Testing strategies
-
Comprehensive Coverage
- Edge cases consideration
- Error handling tasks
- Monitoring setup
- Deployment tasks
Enhanced Output
Research mode typically:
- Generates more detailed tasks
- Includes industry standards
- Adds compliance considerations
- Suggests modern tooling
When to Use
- New technology domains
- Complex requirements
- Regulatory compliance needed
- Best practices crucial
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.
- 7d ago First seen · 48 lines · 0 tokens per session scan A 3efdc825c89e
parse-prd-with-research is a command published in the GitHub repository TICnine/autotask-mcp (0 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 215 tokens. A static security scan graded it A with 0 findings. It is 100% identical to parse-prd-with-research, differing in 0 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.