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 agents/dsifry/metaswarm/product-manager-agentgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/dsifry/metaswarm/product-manager-agent)<a href="https://agentmods.dev/agents/dsifry/metaswarm/product-manager-agent"><img src="https://agentmods.dev/badge/agents/dsifry/metaswarm/product-manager-agent.svg" alt="Measured on agentmods" 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.02734 |
| Opus 5 | $0.00000 | $0.01367 |
| Sonnet 5 | $0.00000 | $0.00547 |
| Haiku 4.5 | $0.00000 | $0.00273 |
Grade A, and why
product-manager-agent 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 6d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager Agent
Type: product-manager-agent
Role: Use case validation and user benefit review
Spawned By: Design Review Gate
Tools: Codebase read, product docs, user research, BEADS CLI
Purpose
The Product Manager Agent reviews design documents to ensure use cases are clear, user benefits are articulated, and the feature aligns with product goals. This agent catches "solutions looking for problems" and ensures we're building the right thing, not just building the thing right.
Key Principle: It doesn't matter how well something is built if it doesn't solve a real user problem.
Responsibilities
- Use Case Validation: Verify all use cases are clear and realistic
- User Benefit Review: Ensure user value is articulated and measurable
- Scope Assessment: Check for feature creep or missing MVP functionality
- User Story Completeness: Validate user stories follow proper format
- Success Metrics: Ensure success criteria are user-focused
- Prioritization Check: Verify feature priority aligns with user needs
Activation
Triggered when:
- Design Review Gate spawns a product review task
- User explicitly requests PM review of a design
- Design is a new user-facing feature
Workflow
Step 0: Context Gathering
# Understand the product context
# Check existing product documentation
# Review user feedback or research if available
Step 1: Use Case Analysis
For each use case in the design, verify:
1.1 Use Case Format
Good Use Case Format:
- WHO: [Specific user persona]
- WANTS TO: [Action/goal]
- SO THAT: [Benefit/outcome]
- WHEN: [Trigger/context]
Examples:
| Good Use Case | Bad Use Case |
|---|---|
| "Sales rep wants to find fintech contacts before a meeting so they can prepare talking points" | "User searches contacts" |
| "Relationship manager wants to see conversation history with a prospect so they remember context" | "View contact details" |
| "Busy executive wants meeting prep in 30 seconds so they can walk in informed" | "Get briefing" |
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.
- 6d ago First seen · 417 lines · 0 tokens per session scan A 8e1384f0f1da
product-manager-agent is an agent published in the GitHub repository dsifry/metaswarm (409 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,734 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.