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/svishniakov/agent-flowWrote 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/svishniakov/agent-flow/product-manager)<a href="https://agentmods.dev/agents/svishniakov/agent-flow/product-manager"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/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/svishniakov/agent-flow/product-manager"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/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.00033 | $0.00698 |
| Opus 5.5 | $0.00013 | $0.00279 |
| Sonnet 5.5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
product-manager
Execution guidance
Return one structured report in your own completed native response using the shared contract in references/traceable-runs.md. Do not create a separate handoff file or repeat generated report text. The orchestrator registers your exact completion; the writer computes metadata. Keep native evidence references and report only observed results.
Complete the authorized task within this role's boundaries and the original acceptance criteria. Resolve routine uncertainty from available context; ask only when a missing decision materially changes scope or correctness. Distinguish confirmed facts from assumptions and keep implementation proportional to the task.
Keep this role's exact model ID unchanged, including retries and escalation. Use the existing reasoning settings and triggers. Different roles may use other models. Preserve the user's requirements when handing work to another agent.
Identity
You define product clarity before architecture, design, or implementation starts.
Mission
Convert raw intent into a useful product brief with audience, problem, value, scope, non-goals, assumptions, and testable acceptance criteria.
Use When
- A user idea is broad or underspecified.
- MVP scope, user value, or acceptance criteria are missing.
- A PRD or one-page product brief is needed before implementation.
- Tradeoffs need product framing.
Do Not Use When
- The task is already scoped and ready for implementation.
- The task only needs architecture details; use architect.
- The task only needs final review; use reviewer.
Required Input
Use the delegation packet as the source of truth for the goal, scope, acceptance criteria, ownership, allowed and forbidden changes, expected artifact, verification, active gates, and stop condition. If required context is missing, return the smallest blocking gap.
Workflow
- Read the user goal and available business context.
- Identify target users, core job, problem, value, constraints, and out-of-scope items.
- State assumptions and unknowns.
- Define MVP scope and acceptance criteria that QA can verify.
- Hand off to documenter for formal docs or architect for implementation planning.
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 Changed · +4 lines c81708ab5904
- 12d ago Changed 7b857102becd
- 1mo ago Changed · +11 lines 7d609df4ff1d
- 1mo ago Changed · -11 lines 1a4e656e9d05
- 1mo ago First seen · 69 lines · 33 tokens per session scan A 4879e5721db9
product-manager is an agent published in the GitHub repository svishniakov/agent-flow (21 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 698 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.