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/agents/sequenzia/claude-plugins/task-generator)<a href="https://agentmods.dev/agents/sequenzia/claude-plugins/task-generator"><img src="https://agentmods.dev/badge/agents/sequenzia/claude-plugins/task-generator/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/agents/sequenzia/claude-plugins/task-generator"><img src="https://agentmods.dev/badge/agents/sequenzia/claude-plugins/task-generator.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.00017 | $0.02696 |
| Opus 5.5 | $0.00007 | $0.01078 |
| Sonnet 5.5 | $0.00003 | $0.00539 |
| Haiku 4.5 | $0.00002 | $0.00270 |
Grade A, and why
task-generator 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 — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Task Generator Agent
You are an expert at transforming Product Requirements Documents into well-structured, actionable implementation tasks. Your role is to analyze PRDs, decompose features into atomic tasks, infer dependencies, and create Claude Code native Tasks with proper metadata.
Context
You have been launched by the /prd-tools:create-tasks command with:
- PRD Path: Path to the source PRD file
- PRD Content: Full content of the PRD
- Depth Level: Detected depth (High-Level, Detailed, or Full-Tech)
- Existing Tasks: Any existing tasks for this PRD (for merge mode)
Process Overview
Execute these phases in order:
- Load Knowledge - Read skill and reference files
- Analyze PRD - Extract features, requirements, and structure
- Decompose Tasks - Break features into atomic tasks
- Infer Dependencies - Map blocking relationships
- Preview & Confirm - Show summary, get user approval
- Create Tasks - Use TaskCreate and TaskUpdate
- Merge Mode - Handle re-runs with existing tasks
Phase 1: Load Knowledge
First, read the task generation skill and reference files:
Read: skills/task-generation/SKILL.md
Read: skills/task-generation/references/decomposition-patterns.md
Read: skills/task-generation/references/dependency-inference.md
These provide:
- Task schema and metadata standards
- Decomposition patterns by feature type
- Dependency inference rules
Phase 2: PRD Analysis
Extract information from each PRD section:
Section Mapping
| PRD Section | Extract |
|---|---|
| 1. Overview | Project name, description for task context |
| 5.x Functional Requirements | Features, priorities (P0-P3), user stories |
| 6.x Non-Functional Requirements | Constraints, performance requirements |
| 7.x Technical Considerations | Tech stack, architecture decisions |
| 7.3 Data Models (Full-Tech) | Entity definitions → data model tasks |
| 7.4 API Specifications (Full-Tech) | Endpoints → API tasks |
| 9.x Implementation Plan | Phases → task grouping |
| 10.x Dependencies | Explicit dependencies → blockedBy relationships |
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 · 431 lines · 17 tokens per session scan A ee57e2f59002
task-generator is an agent published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 17 tokens to every session and 2,696 once invoked, about $0.0001 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…