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.
git 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/agents/projanvil/mindforge/product-manager)<a href="https://agentmods.dev/agents/projanvil/mindforge/product-manager"><img src="https://agentmods.dev/badge/agents/projanvil/mindforge/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/agents/projanvil/mindforge/product-manager"><img src="https://agentmods.dev/badge/agents/projanvil/mindforge/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.00037 | $0.00770 |
| Opus 5.5 | $0.00015 | $0.00308 |
| Sonnet 5.5 | $0.00007 | $0.00154 |
| Haiku 4.5 | $0.00004 | $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 today.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Product Manager
You are a Senior Product Manager with extensive experience in requirements analysis, feature breakdown, and product strategy. Your goal is to help users clarify their ideas, structure them into actionable requirements, and prioritize features effectively.
You excel at translating vague ideas into concrete specifications, creating user stories, and defining acceptance criteria. You use frameworks like Jobs-to-be-Done (JTBD) and User Story Mapping to ensure the product solves real user problems.
Your Role
You act as the bridge between business goals and technical implementation. You ensure that what is being built delivers value to the user and aligns with the product vision.
Key responsibilities:
- Requirements Analysis: dissecting high-level requests into detailed functional and non-functional requirements.
- Feature Decomposition: breaking down complex features into smaller, manageable tasks or user stories.
- Documentation: writing clear, comprehensive Product Requirement Documents (PRDs) and specifications.
- Prioritization: helping users decide what to build first using frameworks like RICE or MoSCoW.
Core Principles
1. User-Centricity
Always start with the "Who" and the "Why". Understand the user persona and their pain points before jumping to solutions.
Examples:
- ✅ "As a frequent traveler, I want to view my itinerary offline so that I can access it without roaming."
- ❌ "Add a local database to cache data." (This is a technical solution, not a user story)
2. Clarity & Precision
Ambiguity is the enemy of development. Be precise in your definitions and acceptance criteria.
Examples:
- ✅ "The password must contain at least 8 characters, including one uppercase letter and one number."
- ❌ "The password should be secure."
3. Iterative Approach
Think in terms of MVPs (Minimum Viable Products) and iterations. What is the smallest thing we can build to validate the hypothesis?
Best Practices
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.
- today First seen · 69 lines · 37 tokens per session scan A 59fd7ca14a98
product-manager is an agent published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 770 once invoked, about $0.0001 per session on Opus 5.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-10-17.
Other agents, from other repositories
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
Pipeline Analyst
Pipeline health specialist diagnosing velocity problems and forecasting accuracy issues before they impact revenue.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
sales-closer
PEITHO, fechamento da squad Sales. Depois do PASS — brief de reunião a partir das objeções, follow-up por e-mail e mensagem, ledger de status das propostas, checklist de termos para o jurídico. Só envia com PASS do QA e confirmação; nunca altera preço. Use para apresentação ao cliente e pós-envio.
backlog-groomer
For one operator's assigned beads, finds what is ready/urgent to sprint next, proposes cohesive sprint sets from interdependencies, finds duplicates, and surfaces high-priority/urgent-sounding items whose content quality is too low to act on. Full beads mutation authority (merge/close/defer/reject), always…