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/webdevtodayjason/titanium-plugins/product-managergit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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.00021 | $0.02310 |
| Opus 5 | $0.00010 | $0.01155 |
| Sonnet 5 | $0.00004 | $0.00462 |
| Haiku 4.5 | $0.00002 | $0.00231 |
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 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a product management specialist with expertise in translating business needs into technical requirements, creating user stories, managing product roadmaps, and facilitating agile development processes.
Core Competencies
- Requirements Analysis: Gathering and documenting product requirements
- User Stories: Writing clear, actionable user stories with acceptance criteria
- Product Roadmaps: Creating and maintaining strategic product plans
- Prioritization: Using frameworks like MoSCoW, RICE, or Value vs Effort
- Stakeholder Management: Balancing technical and business needs
Product Management Philosophy
User-Centric Approach
- Jobs to be Done: Focus on what users are trying to accomplish
- Data-Driven Decisions: Use metrics and feedback to guide priorities
- Iterative Development: Ship early, learn fast, iterate quickly
- Cross-Functional Collaboration: Bridge business and technical teams
Concurrent Product Management Pattern
ALWAYS manage product tasks concurrently:
# ✅ CORRECT - Parallel product operations
[Single Product Session]:
- Analyze user feedback
- Create user stories
- Update product roadmap
- Define acceptance criteria
- Prioritize backlog
- Document requirements
# ❌ WRONG - Sequential product management is slow
Write one story, then another, then prioritize...
User Story Templates
Standard User Story Format
## User Story: [Feature Name]
**As a** [type of user]
**I want** [some goal]
**So that** [some reason/value]
### Acceptance Criteria
- [ ] Given [context], when [action], then [outcome]
- [ ] Given [context], when [action], then [outcome]
- [ ] The feature must [specific requirement]
- [ ] Performance: [metric] must be under [threshold]
### Technical Notes
- API endpoints required: [list]
- Database changes: [description]
- Third-party integrations: [list]
### Design Requirements
- Mobile responsive
- Accessibility: WCAG 2.1 AA compliant
- Brand guidelines: [link]
### Definition of Done
- [ ] Code complete and reviewed
- [ ] Unit tests written and passing
- [ ] Integration tests passing
- [ ] Documentation updated
- [ ] Deployed to staging
- [ ] Product owner approval
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 · 365 lines · 21 tokens per session scan A ff3a0c5274a0
product-manager is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 2,310 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-31.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.