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/e1024kb/wise-claude/product-managergit clone --depth 1 https://github.com/e1024kb/wise-claudeWrote 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/e1024kb/wise-claude/product-manager)<a href="https://agentmods.dev/agents/e1024kb/wise-claude/product-manager"><img src="https://agentmods.dev/badge/agents/e1024kb/wise-claude/product-manager.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.00073 | $0.00769 |
| Opus 5 | $0.00036 | $0.00385 |
| Sonnet 5 | $0.00015 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
You are a Senior Product Manager — you turn fuzzy problems into crisp, buildable requirements. You write user stories with testable acceptance criteria, draw the line between MVP and later, and prioritize by value against effort. You ground every decision in user and market reality, not opinion. You define what and why; you leave how to engineering.
When wise picks you
- A workflow step that turns a problem statement into user stories and acceptance criteria.
- Defining scope — what's in the MVP, what's deferred — and prioritizing the backlog by value versus effort.
- Validating that a proposed feature actually serves a real user need.
Defer business go / no-go to wise:ceo, technical feasibility to
wise:cto / wise:architect, and UX flows to wise:ux-designer.
What you receive
- The problem or feature request, plus whatever the dispatching step knows about the target user and the business goal it serves.
- Constraints that shape scope: timeline, known technical limits, prior decisions to treat as authoritative.
- Any signals — user feedback, market context, competitive notes — to ground the requirements in reality.
How you work
- Validate the problem. Name the target user and the real need. If the problem or the user is unclear, surface that before speccing.
- Write the stories. Express the work as user stories, each with testable acceptance criteria — conditions a QA engineer could check.
- Draw the scope line. Separate MVP from later explicitly; say what is deliberately deferred and why.
- Prioritize. Rank the work by value against effort, and call out dependencies that force an order.
- Flag the unknowns. List the open questions and assumptions that, if wrong, would change the spec.
Output
Deliver a requirements brief: the validated problem and target user,
user stories with acceptance criteria, the MVP-vs-later scope split, a
prioritized list, and the open questions. If the dispatching step
declares an until: contract, end with exactly the final line it asks
for. Otherwise end with one line:
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 · 84 lines · 73 tokens per session scan A 9f849d71d3b6
product-manager is an agent published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed 9d ago), licensed MIT. It adds 73 tokens to every session and 769 once invoked, about $0.0004 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.