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/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/issue-prd-generation)<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/issue-prd-generation"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/issue-prd-generation/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/rjmurillo/ai-agents/issue-prd-generation"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/issue-prd-generation.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.00000 | $0.01461 |
| Opus 5 | $0.00000 | $0.00731 |
| Sonnet 5 | $0.00000 | $0.00292 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
issue-prd-generation 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 2d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generation Task
You are generating a comprehensive Product Requirements Document (PRD) for a GitHub issue. This PRD will be passed to a separate AI agent instance with ONLY THIS CONTEXT for implementation. Write with that constraint in mind.
Quality Expectations
This is customer-facing work. The PRD must be:
- Rich: Comprehensive analysis, not surface-level summaries
- Exceptional: Stand-alone document that enables action without follow-up questions
- Rigorous: Evidence-based claims, clearly flagged assumptions
- Thoughtful: Anticipate blockers, surface unknowns, propose decision paths
Required Sections
1. Executive Summary
- One-paragraph problem statement
- Key findings table with status indicators
- Clear verdict: BLOCKED, READY, PARTIAL, or REQUIRES_DISCOVERY
| Scope | Status | Blocker |
|-------|--------|---------|
| Primary ask | Status emoji | Blocker description or "None" |
| Secondary ask | Status emoji | ... |
Status emojis: :red_circle: BLOCKED, :yellow_circle: PARTIAL, :green_circle: READY
2. Problem Statement
- Current State: What exists today (table format preferred)
- Gap Analysis: What's missing and why it matters
- User Impact: Who is affected and how
3. Research Findings
Conduct thorough research before writing requirements:
- Primary Sources: Official documentation, release notes, specifications
- Secondary Sources: Community discussions, blog posts, tutorials
- Empirical Data: If applicable, observed behavior or test results
Document findings with:
- Direct quotes (when brief and relevant)
- Source links
- Confidence levels (CONFIRMED, LIKELY, UNCERTAIN)
4. Proposed Solution
Structure as phases with clear dependencies:
### Phase 1: [Name] (Status: READY/BLOCKED/DEPENDS)
**Estimated Effort**: S/M/L
**Blockers**: None / List blockers
| Task | Description |
|------|-------------|
| 1.1 | Task description |
5. Functional Requirements
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.
- 2d ago First seen · 223 lines · 0 tokens per session scan A b4f50de1a939
issue-prd-generation is a command published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,461 tokens. 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-09-06.
Other commands, from other repositories
workflow-manager
Process automation with TodoWrite planning and Task execution.
commands
A set of project-management commands for maintaining collaboration rules, documentation, plans, thoughts, and project configuration. It covers tasks such as adding commands, updating governance instructions, recording ideas, and organizing roadmap items.
portfolio-status
Review the health of all projects in the portfolio.
sdlc-ship
Phase 4 — Ship. Runs devops-engineer for CI/CD, cloud deploy, and release. Reads verify-handoff.md for clean context.
issue-tracker
Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination.
workflow-create
Command "workflow-create" from airmcp-com/mcp-standards, covering workflow-create, usage, options, examples and create workflow.