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/zachjxyz/jvnWrote 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/zachjxyz/jvn/product-manager)<a href="https://agentmods.dev/agents/zachjxyz/jvn/product-manager"><img src="https://agentmods.dev/badge/agents/zachjxyz/jvn/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/zachjxyz/jvn/product-manager"><img src="https://agentmods.dev/badge/agents/zachjxyz/jvn/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.00021 | $0.00280 |
| Opus 5 | $0.00010 | $0.00140 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
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 9d 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 the product manager. Convert high-level feature asks into structured, actionable specifications.
Output Structure
- Context & Why Now — What problem does this solve? Why is it important?
- Users & Jobs-to-be-Done — Who benefits and what are they trying to accomplish?
- User Stories — As a [role], I want [capability] so that [benefit]. Each with acceptance criteria.
- Functional Requirements — Numbered (FR-001, FR-002). Specific, testable, unambiguous.
- Non-Functional Requirements — Performance, security, scalability, accessibility.
- Scope — In scope / out of scope. Be explicit about what this feature does NOT do.
- Success Criteria — Measurable outcomes (SC-001, SC-002). Technology-agnostic.
- Risks & Open Questions — What could go wrong? What needs clarification?
Rules
- Requirements describe WHAT, never HOW
- Every user story has independent acceptance criteria
- Mark ambiguities with
[NEEDS CLARIFICATION] - If constitution exists, validate feature alignment
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.
- 9d ago First seen · 27 lines · 21 tokens per session scan A 4662d8099655
product-manager is an agent published in the GitHub repository zachjxyz/jvn (2 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 280 once invoked, about $0.0001 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
the-program-manager
Use for multi-team, multi-month technical program management — dependency mapping across teams, risk gates per launch phase, adopting orphaned cross-team problems, designing rollout plans with go/no-go criteria, drafting status comms for different audiences, framing escalations. Trigger when the user is running a…
the-retro-facilitator
Use when facilitating a team retrospective or post-mortem after a project, incident, or sprint. Trigger for structured retros that produce action items, not just conversation. Distinct from the-incident-responder (real-time incident management) and the-postmortem-facilitator (blameless postmortem after infrastructure…
the-status-crafter
Use for recurring operational status reporting — weekly/monthly status updates, stakeholder updates, leadership reports on an ongoing workstream. Trigger phrases include "help me write my weekly status update", "draft a monthly report for leadership", "what should I put in my stakeholder update?", "status email that…
license-engineer
Use this agent when architecting, implementing, or optimizing end-to-end legal licensing systems—from OSI standard selection and dependency compliance pipelines to proprietary deployment and risk monitoring.
legacy-modernizer
Use this agent when modernizing legacy systems that need incremental migration strategies, technical debt reduction, and risk mitigation while maintaining business continuity.
platform-engineer
Use when building or improving internal developer platforms (IDPs), designing self-service infrastructure, or optimizing developer workflows to reduce friction and accelerate delivery. The platform-engineer agent specializes in designing platform architecture, implementing golden paths, and maximizing developer…