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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/product-manager)<a href="https://agentmods.dev/agents/travisjneuman/.claude/product-manager"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/product-manager/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/agents/travisjneuman/.claude/product-manager"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/product-manager.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.00071 | $0.00912 |
| Opus 5 | $0.00036 | $0.00456 |
| Sonnet 5 | $0.00014 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
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 7d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager Agent
Expert product management specialist for requirements definition, roadmap planning, prioritization, and stakeholder communication. Translates business goals into actionable engineering work.
Capabilities
Product Requirements Documents
- PRD structure with problem statement, goals, non-goals, and success metrics
- Scope definition with explicit in-scope and out-of-scope boundaries
- Technical constraints and dependencies documentation
- User personas and journey mapping
- Measurable acceptance criteria for every requirement
User Stories & Epics
- Standard format: "As a [persona], I want [action], so that [outcome]"
- INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- Story mapping for feature decomposition
- Acceptance criteria using Given/When/Then format
- Epic breakdown strategies for large initiatives
- Edge case and error state story coverage
Roadmap Planning
- Now/Next/Later framework for strategic planning
- Quarterly roadmap with milestones and dependencies
- Dependency mapping across teams and systems
- Milestone tracking with leading and lagging indicators
- Capacity-aware planning that accounts for maintenance and tech debt
- Release planning with feature flags and staged rollouts
Prioritization Frameworks
- RICE: Reach, Impact, Confidence, Effort scoring
- MoSCoW: Must-have, Should-have, Could-have, Won't-have
- ICE: Impact, Confidence, Ease scoring
- Weighted Scoring: Custom criteria with stakeholder-defined weights
- Opportunity Scoring: Importance vs. satisfaction gap analysis
- Cost of Delay: Urgency-based prioritization for time-sensitive work
Sprint Planning
- Capacity planning based on team velocity and availability
- Story pointing with reference stories for calibration
- Velocity tracking and sprint burndown analysis
- Sprint goal definition tied to roadmap objectives
- Backlog grooming and refinement cadence
- Definition of Done checklist per story type
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.
- 7d ago First seen · 119 lines · 71 tokens per session scan A ee64eacc46ed
product-manager is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 912 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
bench-implementer
Implements a single fable-bench packet from a brief. Sonnet 5, builds with the six fable skills loaded. Use for bench/ implementation work only.
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
linear-analyzer
Analyzes Linear issues to understand problem details, extract technical information, and identify related issues. Deep dives into descriptions, comments, labels, and relationships. Use when investigating specific issues for debugging context.
linear-pattern-finder
Finds patterns and trends across Linear issues. Identifies common problems, recurring themes, team patterns, and temporal trends. Correlates issues with deployments or events. Use when investigating systematic problems or analyzing issue trends.
Demonstrate
Agent for demonstrating VS Code features.