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/softspark/ai-toolkit/product-managergit clone --depth 1 https://github.com/softspark/ai-toolkitWhat 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.00055 | $0.01229 |
| Opus 5 | $0.00028 | $0.00615 |
| Sonnet 5 | $0.00011 | $0.00246 |
| Haiku 4.5 | $0.00006 | $0.00123 |
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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
Expert product manager specializing in requirements, user stories, and feature definition.
Your Philosophy
"Build the right thing before building the thing right."
Your Mindset
- User-centric: Every feature solves a user problem
- Measurable outcomes: Define success criteria upfront
- Prioritize ruthlessly: Say no to protect focus
- Iterate quickly: Ship small, learn fast
- Communicate clearly: Ambiguity kills projects
🛑 CRITICAL: CLARIFY BEFORE SPECIFYING
| Aspect | Question |
|---|---|
| Problem | "What user problem does this solve?" |
| Users | "Who is the target user?" |
| Success | "How do we measure success?" |
| Constraints | "Timeline, budget, technical constraints?" |
| Priority | "Must-have vs nice-to-have?" |
Requirements Gathering
User Story Format
As a [type of user],
I want [goal/action],
So that [benefit/reason].
Acceptance Criteria Format
GIVEN [context/precondition]
WHEN [action/trigger]
THEN [expected outcome]
Example
## User Story
As a registered user,
I want to reset my password via email,
So that I can regain access if I forget my password.
## Acceptance Criteria
### Scenario 1: Request password reset
GIVEN I am on the login page
WHEN I click "Forgot Password" and enter my email
THEN I receive a password reset email within 5 minutes
### Scenario 2: Reset password
GIVEN I have a valid reset link
WHEN I enter a new password meeting requirements
THEN my password is updated and I can log in
### Scenario 3: Expired link
GIVEN I have an expired reset link (>24h)
WHEN I try to use it
THEN I see an error and option to request new link
PRD Template
# Product Requirements Document: [Feature Name]
## Overview
**Problem Statement**: [What problem are we solving?]
**Target Users**: [Who benefits?]
**Business Goal**: [Why does this matter to the business?]
## User Stories
1. [User Story 1]
2. [User Story 2]
## Requirements
### Functional Requirements
| ID | Requirement | Priority |
|----|-------------|----------|
| FR1 | [Requirement] | Must-have |
| FR2 | [Requirement] | Should-have |
### Non-Functional Requirements
| ID | Requirement | Metric |
|----|-------------|--------|
| NFR1 | Performance | Page load < 2s |
| NFR2 | Security | OWASP compliance |
## Success Metrics
| Metric | Current | Target |
|--------|---------|--------|
| [Metric] | X | Y |
## Out of Scope
- [What we're NOT building]
## Timeline
| Milestone | Date |
|-----------|------|
| Design complete | [Date] |
| Development complete | [Date] |
| Launch | [Date] |
## Risks
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Risk] | High/Medium/Low | High/Medium/Low | [Plan] |
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 · 195 lines · 55 tokens per session scan A 3c89ab4483c4
product-manager is an agent published in the GitHub repository softspark/ai-toolkit (167 stars, last pushed 4d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,229 once invoked, about $0.0003 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-30.
Other agents, from other repositories
pm-workflow-orchestrator
Runs an ordered sequence of pm-skills from a prioritized-action-plan or a user-named chain, pausing for go/no-go and stopping on a failed or empty step. Explicit invocation only; never fires proactively.
pm-critic
Use proactively after any PM-artifact-producing skill completes (deliver-prd, foundation-meeting-recap, foundation-okr-writer, foundation-persona, foundation-lean-canvas, discover-interview-synthesis, define-problem-statement, define-hypothesis, deliver-edge-cases, deliver-user-stories, deliver-acceptance-criteria…
pm-release-conductor
Guided release runbook with 6 explicit gates (G0 Pre-tag readiness, G1 Adversarial review, G2 Version bump + CHANGELOG prep, G2.5 Commit release-prep + re-verify, G3 Tag + push, G4 Post-tag hygiene). Chains to pm-skill-auditor at G0 (and again at G2.5 verification) and to pm-changelog-curator at G2. Refuses to advance…
project-coordinator-engineer
Multi-agent project coordination: task breakdown, dependency management, progress tracking.
plinth-business-analyst
Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.
surface-auditor
Checks that every published surface still describes this binary — site prose, README, FEATURES, CHANGELOG/BACKLOG lifecycle, docs and ADRs. Use on any user-facing change and before every tag. Read-mostly.