A guided template for writing a Product Requirements Document (PRD), a document that describes what a product or software system should do. It gathers the agency’s purpose, agent roles, communication, tools, and outside services.

Use it to plan a group of cooperating software agents, define their jobs, and document the tools and services they need.

It turns an early idea into a written plan before implementation begins. This makes missing responsibilities, integrations, and communication paths easier to identify.

create-prd — Command for Claude Code and Cursor by AlexFischman

Install

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.

Clone the repo

git clone --depth 1 https://github.com/AlexFischman/mcp-skill-creator-agency

Made for: Claude Code, Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/alexfischman/mcp-skill-creator-agency/create-prd/github.svg)](https://agentmods.dev/commands/alexfischman/mcp-skill-creator-agency/create-prd)

Your own site

<a href="https://agentmods.dev/commands/alexfischman/mcp-skill-creator-agency/create-prd"><img src="https://agentmods.dev/badge/commands/alexfischman/mcp-skill-creator-agency/create-prd/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/alexfischman/mcp-skill-creator-agency/create-prd"><img src="https://agentmods.dev/badge/commands/alexfischman/mcp-skill-creator-agency/create-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,069 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.01069
Opus 5	$0.00000	$0.00535
Sonnet 5	$0.00000	$0.00214
Haiku 4.5	$0.00000	$0.00107

Measured 9d ago against content hash 6e51c2069a14, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

create-prd 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 9d 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.

Origin

This is a copy

100% identical to create-prd — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/commands/create-prd.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PRD Creation - Product Requirements Document for Agency Swarm

Your task is to create a Product Requirements Document (PRD) that defines the agency structure, agent roles, and tool specifications.

Step 1: Ask Questions

Ask the user for:

Agency Name
Purpose: What does the agency do?
Agent Roles: What roles are needed?
Communication Flows: How do agents communicate?
Tools per Agent: What actions should each agent perform?
External Integrations: What APIs or services will be used?

Step 2: Research

Search for available MCP servers for the systems user wants to connect to.

MCP Search Priority:

Check official registry: https://github.com/mcp
Search using web search: mcp server <system name>
If not MCP server is found, search for API documentation and create a custom tool that wraps the API call.

Common MCP Servers:

@modelcontextprotocol/server-filesystem - File operations
@modelcontextprotocol/server-github - GitHub
@modelcontextprotocol/server-slack - Slack
@modelcontextprotocol/server-postgres - PostgreSQL
@modelcontextprotocol/server-sqlite - SQLite
@modelcontextprotocol/server-puppeteer - Web automation
@modelcontextprotocol/server-brave-search - Web search

Built-in Tools:

WebSearchTool - Built-in web search (use this instead of MCP for web search)

For each integration:

Document MCP server package name if found
Note required API keys and how to obtain them
If no MCP exists, note that custom tool will be needed

Step 3: Create PRD

Create ./prd.txt using this template:

# [Agency Name]

---

- **Purpose:** [High-level description: what the agency achieves, target market, value proposition]

- **Communication Flows:**
  - **Between Agents:**
    - [Description of protocols and flows between agents, shared resources, data exchange]
    - **Example Flow:**
      - **[Agent A] -> [Agent B]:** [Trigger conditions, interaction description, expected outcomes]
      - **[Agent B] -> [Agent C]:** [Trigger conditions, interaction description, expected outcomes]
  - **Agent to User Communication:** [How agents communicate with users, interfaces, channels]

---

## [Agent Name]

### Role within the Agency

[Description of realistic job role and responsibilities - model after actual professions]

### Tools

- **[ToolName]:**
  - **Description**: [What this tool does and when it's used - must be a real-world task]
  - **Inputs**:
    - [name] (type) - description
  - **Validation**:
    - [Condition] - description
  - **Core Functions:** [Main functions the tool performs]
  - **APIs**: [List of APIs used, if any]
  - **Output**: [Expected output format - string or JSON object]
- **MCP Name**: [MCP server package name if found]
  - **URL**: [Url of the server’s github / official page]
  - **Authentication**: [How the MCP is authenticated]
  - **Allowed Tools**: [Which tools to allow]

---

[...repeat for each agent]

Read the full file on GitHub · 137 lines

Changes

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.

9d ago First seen · 137 lines · 0 tokens per session scan A 6e51c2069a14

Subscribe to this mod's changes

create-prd is a command published in the GitHub repository AlexFischman/mcp-skill-creator-agency (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,069 tokens. A static security scan graded it A with 0 findings. It is 100% identical to create-prd, differing in 0 lines, and is treated as a copy.

Planning Writing and docs agency-swarm ai-agents claude-skills docker fastapi mcp

create-prd

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

PRD Creation - Product Requirements Document for Agency Swarm

Step 1: Ask Questions

Step 2: Research

Step 3: Create PRD

What this file has done since we first saw it

Other commands, from other repositories

add-endpoint

review

checklist

clarify

specify

analyze