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)<a href="https://agentmods.dev/commands/sequenzia/claude-plugins/create"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/create/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"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/create.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.00011 | $0.00640 |
| Opus 5.5 | $0.00004 | $0.00256 |
| Sonnet 5.5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
create 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generator - Create Command
You are initiating the PRD creation workflow. This process will gather requirements through an interactive interview and generate a comprehensive Product Requirements Document.
Workflow
Step 1: Check for Settings
First, check if there is a settings file at .claude/prd-tools.local.md to get any custom configuration like output path or author name.
Step 2: Gather Initial Information
Use AskUserQuestion to gather the essential starting information with these four questions:
Question 1 - PRD Name:
- Header: "PRD Name"
- Question: "What would you like to name this PRD?"
- Options: Allow text input for a descriptive name
Question 2 - Type:
- Header: "Type"
- Question: "What type of product/feature is this?"
- Options:
- "New product" - A completely new product being built from scratch
- "New feature" - A new feature for an existing product
Question 3 - Depth:
- Header: "Depth"
- Question: "How detailed should the PRD be?"
- Options:
- "High-level overview (Recommended)" - Executive summary with key features and goals
- "Detailed specifications" - Standard PRD with acceptance criteria and phases
- "Full technical documentation" - Comprehensive specs with API definitions and data models
Question 4 - Description:
- Header: "Description"
- Question: "Briefly describe the product/feature and its key requirements"
- Options: Allow text input describing the problem, main features, and constraints
Step 3: Launch Interview Agent
After receiving the initial responses, immediately launch the Interview Agent using the Task tool. Provide this context:
- PRD Name: The name provided by the user
- Product Type: "New product" or "New feature" based on selection
- Depth Level: The selected depth option
- Initial Description: The description provided
- Output Path: From settings or default
specs/PRD-{name}.md - Author: From settings or "Not specified"
The Interview Agent will:
- Conduct an adaptive interview based on the depth level
- Cover all four categories: Problem & Goals, Functional Requirements, Technical Specs, Implementation
- Present a summary for user confirmation before generating the PRD
- Generate the PRD using the appropriate template
- Write the PRD to the configured output path
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 · 80 lines · 11 tokens per session scan A d5837eda0adb
create is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 640 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
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.