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/sequenzia/claude-plugins/generategit clone --depth 1 https://github.com/sequenzia/claude-pluginsWhat 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.00009 | $0.01269 |
| Opus 5 | $0.00005 | $0.00634 |
| Sonnet 5 | $0.00002 | $0.00254 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
generate 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a comprehensive task list from a specification document, organized under a named mission.
Arguments: $ARGUMENTS
Parse the arguments to extract:
- Mission name: First argument (required) - The name for this mission (e.g., "Build User Authentication System")
- Spec document: Second argument (required) - Path to the specification document
If mission name contains spaces, it should be quoted. Example: /mission-control:generate "Build Auth System" specs/auth-spec.md
Analysis Process
-
Read and parse the specification document thoroughly
- Identify all explicit requirements, features, and acceptance criteria
- Extract implicit requirements (error handling, infrastructure, etc.)
- Note constraints and scope boundaries
-
Decompose into atomic tasks
- Each task should have single responsibility
- Tasks should be independent where possible
- Tasks must have clear start/end conditions
- Tasks must be testable with verifiable criteria
-
Map dependencies between tasks
- Identify blocking dependencies: Task B cannot start until Task A completes
- Calculate
blocked_byandblocksrelationships - Flag tasks that are ready to start (no blockers)
-
Assign priorities and complexity
- Priority: critical, high, medium, low (based on dependency depth and risk)
- Complexity: XS, S, M, L, XL (T-shirt sizing)
- When parsing PRDs, map P0=critical, P1=high, P2=medium, P3=low
-
Generate acceptance criteria for each task
- Derive from the specification's acceptance criteria and user stories
- Ensure each criterion is specific and testable
-
Organize into execution phases
- Phase 1: Tasks with no blocking dependencies
- Phase 2+: Tasks whose dependencies are satisfied by previous phases
PRD Integration
When analyzing PRDs from prd-tools:
- Extract features from Section 5 (Functional Requirements)
- Map user stories (US-XXX) to
source_requirements - Convert acceptance criteria items to task
acceptance_criteria - Map P0-P3 priorities to critical/high/medium/low
- Use Section 9 (Implementation Plan) for
execution_phases - Use Section 10 (Dependencies) for task dependencies
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 · 189 lines · 9 tokens per session scan A fc681389368f
generate is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,269 once invoked, about $0.0000 per session on Opus 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.