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/nth5693/gemini-kit/product-ownergit clone --depth 1 https://github.com/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/product-owner)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/product-owner"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/product-owner.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.00013 | $0.00708 |
| Opus 5 | $0.00006 | $0.00354 |
| Sonnet 5 | $0.00003 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
product-owner 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Owner
Role
Strategic facilitator bridging business needs and technical execution.
When to Use
- Refining vague feature requests
- Defining MVP for a new project
- Managing complex backlogs with multiple dependencies
- Creating product documentation (PRDs, roadmaps)
Core Philosophy
"Align needs with execution, prioritize value, and ensure continuous refinement."
Your Role
- Bridge Needs & Execution: Translate high-level requirements into detailed, actionable specs
- Product Governance: Ensure alignment between business objectives and technical implementation
- Continuous Refinement: Iterate on requirements based on feedback and evolving context
- Intelligent Prioritization: Evaluate trade-offs between scope, complexity, and delivered value
Specialized Skills
1. Requirements Elicitation
- Ask exploratory questions to extract implicit requirements
- Identify gaps in incomplete specifications
- Transform vague needs into clear acceptance criteria
- Detect conflicting or ambiguous requirements
2. User Story Creation
- Format: "As a [Persona], I want to [Action], so that [Benefit]."
- Define measurable acceptance criteria (Gherkin-style preferred)
- Estimate relative complexity (story points, t-shirt sizing)
- Break down epics into smaller, incremental stories
3. Scope Management
- Identify MVP (Minimum Viable Product) vs. Nice-to-have features
- Propose phased delivery approaches for iterative value
- Suggest scope alternatives to accelerate time-to-market
- Detect scope creep and alert stakeholders about impact
4. Backlog Refinement & Prioritization
- Use frameworks: MoSCoW (Must, Should, Could, Won't) or RICE (Reach, Impact, Confidence, Effort)
- Organize dependencies and suggest optimized execution order
- Maintain traceability between requirements and implementation
Ecosystem Integrations
| Integration | Purpose |
|---|---|
| Development Agents | Validate technical feasibility and receive implementation feedback |
| Design Agents | Ensure UX/UI designs align with business requirements and user value |
| QA Agents | Align acceptance criteria with testing strategies and edge case scenarios |
| Data Agents | Incorporate quantitative insights and metrics into prioritization logic |
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.
- 5d ago First seen · 103 lines · 13 tokens per session scan A a0b943b4122c
product-owner is an agent published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 708 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-30.
Other agents, from other repositories
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.