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 skills/projanvil/mindforge/product-managementnpx skills add ProjAnvil/MindForge --skill product-managementgit clone --depth 1 https://github.com/ProjAnvil/MindForgeWrote 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/projanvil/mindforge/product-management)<a href="https://agentmods.dev/skills/projanvil/mindforge/product-management"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/product-management.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.00050 | $0.00638 |
| Opus 5 | $0.00025 | $0.00319 |
| Sonnet 5 | $0.00010 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
product-management 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 4d 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 product-management — 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Management Skill
Description
Expertise in product management lifecycle, from ideation to launch. Covers requirements gathering, user story creation, prioritization, and product strategy.
Capabilities
1. Requirements Engineering
- User Interviews & Surveys: Techniques for gathering qualitative and quantitative data.
- Problem Definition: Using "How Might We" statements to frame problems.
- PRD Writing: Structuring comprehensive Product Requirement Documents.
- Functional vs. Non-Functional: Distinguishing between what the system does and how it behaves (performance, security).
2. Feature Prioritization
- RICE Score: Reach, Impact, Confidence, Effort.
- MoSCoW Method: Must have, Should have, Could have, Won't have.
- Kano Model: Delighters, Performance, Basic expectations.
- WSJF: Weighted Shortest Job First (for Agile).
3. User Story Mapping & Definition
- User Story Format: "As a , I want , so that ."
- Acceptance Criteria: Conditions that a software product must satisfy to be accepted by a user.
- INVEST Principle: Independent, Negotiable, Valuable, Estimable, Small, Testable.
4. Product Strategy & Roadmap
- Lean Canvas: 1-page business plan.
- Value Proposition Design: Matching product features to user pains and gains.
- Roadmap Planning: Now, Next, Later frameworks.
Templates
User Story Template
**Title**: [Short description]
**User Story**:
As a [user persona],
I want [action/feature],
So that [benefit/value].
**Acceptance Criteria**:
1. [Criterion 1]
2. [Criterion 2]
3. [Criterion 3]
**Priority**: [High/Medium/Low]
**Notes**: [Additional context]
PRD Structure
- Introduction: Background, Goals, Scope.
- User Personas: Details about target users.
- User Stories: List of features aimed at users.
- Functional Requirements: Specific system behaviors.
- Non-Functional Requirements: Performance, Security, etc.
- UI/UX Guidelines: Wireframes or references.
- Analytics: Metrics to track success.
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.
- 4d ago First seen · 67 lines · 50 tokens per session scan A d26f56be1cc7
product-management is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 638 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to product-management, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
approval-workflows
Configure ServiceNow approval rules and sysapprovalapprover records — manager/group/script approvers, multi-level routing, delegation via sysuserdelegate, and parent-record state rollup.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
hr-service-delivery
Build ServiceNow HR Service Delivery — snhrcorecase from Employee Center or HR catalog, snhrlelifecycleevent onboarding/offboarding with templated activities, and HR document generation.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.