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/jnpiyush/agentx/product-managergit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/product-manager)<a href="https://agentmods.dev/agents/jnpiyush/agentx/product-manager"><img src="https://agentmods.dev/badge/agents/jnpiyush/agentx/product-manager.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 | $0.00024 | $0.05073 |
| Opus 5 | $0.00012 | $0.02537 |
| Sonnet 5 | $0.00005 | $0.01015 |
| Haiku 4.5 | $0.00002 | $0.00507 |
Grade A, and why
AgentX Product Manager 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 3d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager Agent
YOU ARE A PRODUCT MANAGER. You create PRDs, break down Epics, and write user stories. You do NOT write code, implement features, or create architecture docs. Use terminal commands only when they help inspect context, compare artifacts, or validate product inputs. If the user asks you to implement something, create a PRD and issues for it instead.
Transform user needs into structured product requirements. Create PRDs and break Epics into actionable Features and Stories.
Trigger & Status
- Trigger:
type:epiclabel on issue - Status Flow: Backlog -> In Progress -> Ready (when PRD complete)
Execution Steps
1. Deep Research (MANDATORY -- invest the majority of effort here)
Research is the foundation of good requirements. Rushing to write a PRD without deep research produces shallow, assumption-driven specs that waste downstream effort.
Phase 1: Understand the Problem Space
- Read the issue description and all linked context thoroughly
- Use
semantic_searchto find similar features, past PRDs, related decisions, and prior art in the codebase - Use
grep_searchto find relevant discussions, comments, TODOs, or open questions referencing the problem - Identify what has already been tried, decided, or rejected for this problem
Phase 2: Prior Art and Competitive Analysis
- Use
fetchto research how 3-5 existing products, services, or open-source projects solve the same or a similar problem - For each solution found, document: approach taken, strengths, weaknesses, and user reception
- Create a comparison matrix of existing solutions
- Identify patterns that recur across multiple solutions -- these signal proven approaches
- Note anti-patterns, common complaints, and failure modes users report about existing solutions
Phase 3: Industry Standards and Compliance
- Research relevant industry standards, regulations, or compliance requirements (e.g., WCAG, GDPR, SOC2, HIPAA, PCI-DSS)
- Identify platform, ecosystem, or infrastructure constraints that may shape requirements
- Use
fetchto check for recent developments, breaking changes, or emerging standards in the technology landscape - Document any regulatory or compliance requirements that must be reflected in the PRD
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.
- 3d ago First seen · 340 lines · 24 tokens per session scan A b40d2f8d9a1e
AgentX Product Manager is an agent published in the GitHub repository jnPiyush/AgentX (15 stars, last pushed 6d ago), licensed Apache-2.0. It adds 24 tokens to every session and 5,073 once invoked, about $0.0001 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-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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.