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/spjoshis/claude-code-plugins/product-owner-expertgit clone --depth 1 https://github.com/spjoshis/claude-code-pluginsWrote 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/spjoshis/claude-code-plugins/product-owner-expert)<a href="https://agentmods.dev/agents/spjoshis/claude-code-plugins/product-owner-expert"><img src="https://agentmods.dev/badge/agents/spjoshis/claude-code-plugins/product-owner-expert.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.00048 | $0.01020 |
| Opus 5 | $0.00024 | $0.00510 |
| Sonnet 5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
product-owner-expert 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 157 lines · 48 tokens per session scan A 1c51a20e5272
product-owner-expert is an agent published in the GitHub repository spjoshis/claude-code-plugins (6 stars, last pushed 6mo ago), with no licence file. It adds 48 tokens to every session and 1,020 once invoked, about $0.0002 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
triage-issues-and-prs
GitHub issue and PR triage agent for slopus/happy. Use when you need to: review open issues/PRs, find duplicates, identify what needs a reply, close resolved items, draft maintainer responses, or get a status overview of the backlog. Invoke with /triage or when asked about issues, PRs, contributors, or community…
security-reviewer
Reviews the codebase for security vulnerabilities. Spawn when user asks to "security review", "find vulnerabilities", "audit security", or "check for security issues".
architecture-reviewer
Reviews the codebase for architectural issues: structure, coupling, separation of concerns, cohesion, and scalability. Spawn when user asks to "architecture review", "check structure", "review coupling", or "audit separation of concerns".
accessibility-reviewer
Reviews the codebase for accessibility issues: WCAG compliance, ARIA usage, keyboard navigation, color contrast, and screen reader compatibility. Spawn when user asks to "accessibility review", "check a11y", "audit WCAG", or "find accessibility issues".
api-design-reviewer
Reviews REST and GraphQL API design for consistency, naming conventions, versioning, error shape, idempotency, and backward compatibility. Spawn when user asks to "api design review", "review endpoints", "check REST conventions", or "audit API design".
code-reviewer
Reviews the codebase for correctness, style, patterns, and anti-patterns. Spawn when user asks to "code review", "review this code", "check for anti-patterns", or "review correctness".