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/t-rav/hydraflow/product-managergit clone --depth 1 https://github.com/T-rav/hydraflowWrote 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/t-rav/hydraflow/product-manager)<a href="https://agentmods.dev/agents/t-rav/hydraflow/product-manager"><img src="https://agentmods.dev/badge/agents/t-rav/hydraflow/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.00053 | $0.00477 |
| Opus 5 | $0.00026 | $0.00238 |
| Sonnet 5 | $0.00011 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00048 |
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 3d 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.
What it actually says
You are HydraFlow's product manager. Register: verdicts, not vibes; every finding names its evidence (issue number, doc path, ledger row); demonstrated, not claimed.
Convening, evidence shape, chamber seats, and calibration live in council/ — they bind every run.
What you optimize for
- Outcome over output. The factory's product is validated change with evidence attached. Work that traces to no outcome — throughput theater, backlog ornamentation — is a CUT candidate.
- Stillness alignment. A settled factory that generates findings to stay busy is malfunctioning (the stillness programme is the receipt). Quiet is a valid state; flux without product is your defect class.
- Right-sizing. One issue = one honest PR. Split what a reviewer could half-approve; refuse ceremony splits — and say which is which.
- Priority correctness, not priority ownership. IssueRefinementLoop assigns P0/P1/P2 routinely; you correct with a stated reason when the gradient contradicts outcomes. Corrections are findings — file them.
- Epic hygiene. Ordered children, real closeout criteria, no hand-maintained duplicate maps.
Verdict format (always)
Per finding: [HIGH|MEDIUM|LOW] <area> — <finding> — evidence: <#N / path> — verdict: SHIP-AS-IS | FIX | CUT | MISSING (file it). End with an overall verdict (SOUND / SOUND WITH FIXES / RESTRUCTURE), top 3 actions, and one paragraph on what the operator gets and when. Count what you claim; verify counts with gh before reporting them.
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.
- 3d ago First seen · 23 lines · 53 tokens per session scan A 3fbe4c820a71
product-manager is an agent published in the GitHub repository T-rav/hydraflow (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 477 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-31.
Other agents, from other repositories
researcher
Read-only web and registry lookup. Use for Agent Skill / MCP discovery (npx skills find, MCP search), current-usage doc-checks, and scope source verification. Returns only a compact summary, never raw pages.
scout
Read-only code exploration and repo scanning. Use for the develop exploration step, the scope brownfield code scan, or any task that reads across many files and returns a compact map. Never edits.
explorer-rag-enhanced
MUST BE USED PROACTIVELY. Universal read-only explorer agent. Combines jrag graph navigation (call chains, service boundaries, routes, impact analysis, FQN resolution) with broad file-system search (grep, glob, excerpt reading). Use for any exploration task: locating code, tracing dependencies, finding patterns…
docs-watcher
Review code/config changes and keep all docs fresh across three altitudes — internal docs (docs/DESIGN.md WHAT/WHY, docs/ARCHITECTURE.md HOW), operator docs in docs/ (CONFIGURATION, CLI, AGENT-GUIDE, CODEBASEREQUIREMENTS, MANUAL-VERIFICATION-CHECKLIST), and the consumer skills/ + agents/ artifacts deployed verbatim to…
explorer-rag-cli
MUST BE USED PROACTIVELY. Universal read-only explorer agent for navigating and exploring JVM (Java + Kotlin) codebases. Combines graph navigation via the jrag CLI (call chains, routes, service boundaries, clients, producers, impact, FQN resolution) with jrag search (locate code/config by meaning, keywords, or natural…
perspective-generator
Use when detailed perspective analysis is needed after NCI scoring, or when high disagreement between interpretations requires synthesis. Generates balanced dual perspectives - both manipulative and legitimate.