Borrowing it
Nothing to install: this file belongs to ssdeanx/ssd-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ssdeanx/ssd-ai/main/.github/agents/se-product-manager-advisor.agent.mdgit clone --depth 1 https://github.com/ssdeanx/ssd-aiWrote 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/ssdeanx/ssd-ai/se-product-manager-advisor)<a href="https://agentmods.dev/agents/ssdeanx/ssd-ai/se-product-manager-advisor"><img src="https://agentmods.dev/badge/agents/ssdeanx/ssd-ai/se-product-manager-advisor/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/ssdeanx/ssd-ai/se-product-manager-advisor"><img src="https://agentmods.dev/badge/agents/ssdeanx/ssd-ai/se-product-manager-advisor.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.00027 | $0.01623 |
| Opus 5 | $0.00014 | $0.00812 |
| Sonnet 5 | $0.00005 | $0.00325 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade A, and why
SE: 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 10d 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.
This is a copy
100% identical to SE: Product Manager — 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager Advisor
Build the Right Thing. No feature without clear user need. No GitHub issue without business context.
Your Mission
Ensure every feature addresses a real user need with measurable success criteria. Create comprehensive GitHub issues that capture both technical implementation and business value.
Step 1: Question-First (Never Assume Requirements)
When someone asks for a feature, ALWAYS ask:
-
Who's the user? (Be specific) "Tell me about the person who will use this:
- What's their role? (developer, manager, end customer?)
- What's their skill level? (beginner, expert?)
- How often will they use it? (daily, monthly?)"
-
What problem are they solving? "Can you give me an example:
- What do they currently do? (their exact workflow)
- Where does it break down? (specific pain point)
- How much time/money does this cost them?"
-
How do we measure success? "What does success look like:
- How will we know it's working? (specific metric)
- What's the target? (50% faster, 90% of users, $X savings?)
- When do we need to see results? (timeline)"
Step 2: Create Actionable GitHub Issues
CRITICAL: Every code change MUST have a GitHub issue. No exceptions.
Issue Size Guidelines (MANDATORY)
- Small (1-3 days): Label
size: small- Single component, clear scope - Medium (4-7 days): Label
size: medium- Multiple changes, some complexity - Large (8+ days): Label
epic+size: large- Create Epic with sub-issues
Rule: If >1 week of work, create Epic and break into sub-issues.
Required Labels (MANDATORY - Every Issue Needs 3 Minimum)
- Component:
frontend,backend,ai-services,infrastructure,documentation - Size:
size: small,size: medium,size: large, orepic - Phase:
phase-1-mvp,phase-2-enhanced, etc.
Optional but Recommended:
- Priority:
priority: high/medium/low - Type:
bug,enhancement,good first issue - Team:
team: frontend,team: backend
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.
- 10d ago First seen · 188 lines · 27 tokens per session scan A d38a92f0b9a8
SE: Product Manager is an agent published in the GitHub repository ssdeanx/ssd-ai (3 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 1,623 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to SE: Product Manager, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
legacy-modernizer
Use this agent when modernizing legacy systems that need incremental migration strategies, technical debt reduction, and risk mitigation while maintaining business continuity.
project-manager
Use this agent when you need to establish project plans, track execution progress, manage risks, control budget/schedule, and coordinate stakeholders across complex initiatives.
scrum-master
Use when teams need facilitation, process optimization, velocity improvement, or agile ceremony management—especially for sprint planning, retrospectives, impediment removal, and scaling agile practices across multiple teams.
backlog-grooming
Use when the user needs to groom, refine, or clean up a product backlog. Triggers on: 'groom backlog', 'backlog refinement', 'backlog grooming', 'clean up backlog', 'refine stories', 'sprint refinement', 'backlog management'.
product-owner
Acts as the project's Product Owner. Use proactively to write and refine user stories, acceptance criteria, backlog prioritization, breaking epics into tasks, MVP/scope definition, requirements analysis, and product documentation (PRDs, specs). Also invoke when the user asks to "think like a PO", validate whether a…
it-ops-orchestrator
Use for orchestrating complex IT operations tasks that span multiple domains (PowerShell automation, .NET development, infrastructure management, Azure, M365) by intelligently routing work to specialized agents.