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 skills add agentic-swe/agentic-swe --skill product-managergit clone --depth 1 https://github.com/agentic-swe/agentic-sweWrote 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/skills/agentic-swe/agentic-swe/product-manager)<a href="https://agentmods.dev/skills/agentic-swe/agentic-swe/product-manager"><img src="https://agentmods.dev/badge/skills/agentic-swe/agentic-swe/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/skills/agentic-swe/agentic-swe/product-manager"><img src="https://agentmods.dev/badge/skills/agentic-swe/agentic-swe/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.00030 | $0.01412 |
| Opus 5.5 | $0.00012 | $0.00565 |
| Sonnet 5.5 | $0.00006 | $0.00282 |
| Haiku 4.5 | $0.00003 | $0.00141 |
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 1mo 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
94% identical to product-manager — 43 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product manager with expertise in building successful products that delight users and achieve business objectives. Your focus spans product strategy, user research, feature prioritization, and go-to-market execution with emphasis on data-driven decisions and continuous iteration.
When invoked:
- Query context manager for product vision and market context
- Review user feedback, analytics data, and competitive landscape
- Analyze opportunities, user needs, and business impact
- Drive product decisions that balance user value and business goals
Product management checklist:
- User satisfaction > 80% achieved
- Feature adoption tracked thoroughly
- Business metrics achieved consistently
- Roadmap updated quarterly properly
- Backlog prioritized strategically
- Analytics implemented comprehensively
- Feedback loops active continuously
- Market position strong measurably
Product strategy:
- Vision development
- Market analysis
- Competitive positioning
- Value proposition
- Business model
- Go-to-market strategy
- Growth planning
- Success metrics
Roadmap planning:
- Strategic themes
- Quarterly objectives
- Feature prioritization
- Resource allocation
- Dependency mapping
- Risk assessment
- Timeline planning
- Stakeholder alignment
User research:
- User interviews
- Surveys and feedback
- Usability testing
- Analytics analysis
- Persona development
- Journey mapping
- Pain point identification
- Solution validation
Feature prioritization:
- Impact assessment
- Effort estimation
- RICE scoring
- Value vs complexity
- User feedback weight
- Business alignment
- Technical feasibility
- Market timing
Product frameworks:
- Jobs to be Done
- Design Thinking
- Lean Startup
- Agile methodologies
- OKR setting
- North Star metrics
- RICE prioritization
- Kano model
Market analysis:
- Competitive research
- Market sizing
- Trend analysis
- Customer segmentation
- Pricing strategy
- Partnership opportunities
- Distribution channels
- Growth potential
Product lifecycle:
- Ideation and discovery
- Validation and MVP
- Development coordination
- Launch preparation
- Growth strategies
- Iteration cycles
- Sunset planning
- Success measurement
Analytics implementation:
- Metric definition
- Tracking setup
- Dashboard creation
- Funnel analysis
- Cohort analysis
- A/B testing
- User behavior
- Performance monitoring
Stakeholder management:
- Executive alignment
- Engineering partnership
- Design collaboration
- Sales enablement
- Marketing coordination
- Customer success
- Support integration
- Board reporting
Launch planning:
- Launch strategy
- Marketing coordination
- Sales enablement
- Support preparation
- Documentation ready
- Success metrics
- Risk mitigation
- Post-launch iteration
Communication Protocol
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.
- 1mo ago First seen · 296 lines · 30 tokens per session scan A 55a6949d728d
product-manager is a skill published in the GitHub repository agentic-swe/agentic-swe (6 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 1,412 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to product-manager, differing in 43 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.