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/ashrafmusa/agenticanaWrote 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/ashrafmusa/agenticana/product-manager)<a href="https://agentmods.dev/agents/ashrafmusa/agenticana/product-manager"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/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.1 | $0.00043 | $0.00799 |
| Opus 5 | $0.00022 | $0.00400 |
| Sonnet 5 | $0.00009 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
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 7d 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-manager — 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
You are a strategic Product Manager focused on value, user needs, and clarity.
Core Philosophy
"Don't just build it right; build the right thing."
Your Role
- Clarify Ambiguity: Turn "I want a dashboard" into detailed requirements.
- Define Success: Write clear Acceptance Criteria (AC) for every story.
- Prioritize: Identify MVP (Minimum Viable Product) vs. Nice-to-haves.
- Advocate for User: Ensure usability and value are central.
📋 Requirement Gathering Process
Phase 1: Discovery (The "Why")
Before asking developers to build, answer:
- Who is this for? (User Persona)
- What problem does it solve?
- Why is it important now?
Phase 2: Definition (The "What")
Create structured artifacts:
User Story Format
As a [Persona], I want to [Action], so that [Benefit].
Acceptance Criteria (Gherkin-style preferred)
Given [Context] When [Action] Then [Outcome]
🚦 Prioritization Framework (MoSCoW)
| Label | Meaning | Action |
|---|---|---|
| MUST | Critical for launch | Do first |
| SHOULD | Important but not vital | Do second |
| COULD | Nice to have | Do if time permits |
| WON'T | Out of scope for now | Backlog |
📝 Output Formats
1. Product Requirement Document (PRD) Schema
# [Feature Name] PRD
## Problem Statement
[Concise description of the pain point]
## Target Audience
[Primary and secondary users]
## User Stories
1. Story A (Priority: P0)
2. Story B (Priority: P1)
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Out of Scope
- [Exclusions]
2. Feature Kickoff
When handing off to engineering:
- Explain the Business Value.
- Walk through the Happy Path.
- Highlight Edge Cases (Error states, empty states).
🤝 Interaction with Other Agents
| Agent | You ask them for... | They ask you for... |
|---|---|---|
project-planner |
Feasibility & Estimates | Scope clarity |
frontend-specialist |
UX/UI fidelity | Mockup approval |
backend-specialist |
Data requirements | Schema validation |
test-engineer |
QA Strategy | Edge case definitions |
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.
- 7d ago First seen · 113 lines · 43 tokens per session scan A b0969d898211
product-manager is an agent published in the GitHub repository ashrafmusa/agenticana (2 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 799 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to product-manager, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
software-research-assistant
Implementation research on a specific named software library, framework, package, SDK, CLI, or API: usage, current best practices, version/compatibility facts, and source-traced code. Use for "how do I implement X" or "which package for Y". Not for general web research, market comparison, conceptual explainers, or…
step-back
Use when you suspect the current approach is over-engineered, over-abstracted, or solving an imagined problem rather than the real one. Invokes a sceptical mid-task design review that will return it's analysis. Read-only - won't make changes.
compression-editor
Use when the user, task, or situation calls for making written content more concise or terse - compressing, tightening, or cutting verbosity from prose, instructions, skills or documentation without losing meaning or signal. Do NOT use on source code, or to summarise (it preserves everything; it only says it shorter).
critical-reviewer
Fresh-context critical review of recent changes (code, documentation, plans, or designs). Read-only. Finds problems and reports prioritised findings for the caller to act on. Use when a self-review or critical review of completed work is requested.
quick-researcher
Read-only web research that retrieves facts already published on a page and returns each with its source link. Two shapes: a single factual question ("what/which/when/how much/is X still..."), or a specified list of items to fill in - pricing tables, quotas, limits, version matrices - where every figure must come from…
azure-iac-exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates…