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.
git clone --depth 1 https://github.com/sequenzia/claude-pluginsWrote 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/sequenzia/claude-plugins/create-tasks)<a href="https://agentmods.dev/commands/sequenzia/claude-plugins/create-tasks"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/create-tasks/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sequenzia/claude-plugins/create-tasks"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/create-tasks.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.01289 |
| Opus 5.5 | $0.00004 | $0.00516 |
| Sonnet 5.5 | $0.00002 | $0.00258 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
create-tasks 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 1mo 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD to Tasks - Create Tasks Command
You are initiating the task generation workflow. This process reads an existing PRD and creates Claude Code native Tasks with dependencies, priorities, and metadata.
Workflow
Step 1: Validate PRD File
Verify the PRD file exists at the provided path.
If the file is not found:
- Check if user provided a relative path
- Try common PRD locations:
specs/PRD-{name}.mddocs/PRD-{name}.md{name}.mdin current directory
- Use Glob to search for similar filenames:
**/PRD*.md**/*prd*.md**/*requirements*.md
- If multiple matches found, use AskUserQuestion to let user select
- If no matches found, inform user and ask for correct path
Step 2: Read PRD Content
Read the entire PRD file using the Read tool.
Store the full content for passing to the agent.
Step 3: Detect Depth Level
Analyze the PRD content to detect its depth level:
Full-Tech Indicators (check first):
- Contains
API Specificationssection OR### 7.4 APIor similar - Contains API endpoint definitions (
POST /api/,GET /api/, etc.) - Contains
Testing Strategysection - Contains data model schemas with field definitions
- Contains code examples or schema definitions
Detailed Indicators:
- Uses numbered sections (
## 1.,### 2.1) - Contains
Technical ArchitectureorTechnical Considerationssection - Contains user stories (
**US-001**:or similar format) - Contains acceptance criteria (
- [ ]checkboxes) - Contains feature prioritization (P0, P1, P2, P3)
High-Level Indicators:
- Contains feature table with Priority column
- Executive summary focus (brief problem/solution)
- No user stories or acceptance criteria
- Shorter document (~50-100 lines)
- Minimal technical details
Detection Priority:
- If Full-Tech indicators found → Full-Tech
- Else if Detailed indicators found → Detailed
- Else if High-Level indicators found → High-Level
- Default → Detailed
Step 4: Check for Existing Tasks
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.
- 1mo ago First seen · 190 lines · 10 tokens per session scan A 8d43dd37c6d5
create-tasks is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 1,289 once invoked, about $0.0000 per session on Opus 5.5. 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.