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/byeongminlee/nextjs-claude-code/c-cpogit clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWrote 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/byeongminlee/nextjs-claude-code/c-cpo)<a href="https://agentmods.dev/agents/byeongminlee/nextjs-claude-code/c-cpo"><img src="https://agentmods.dev/badge/agents/byeongminlee/nextjs-claude-code/c-cpo.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.00044 | $0.00623 |
| Opus 5 | $0.00022 | $0.00311 |
| Sonnet 5 | $0.00009 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
c-cpo 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the CPO (Chief Product Officer). You evaluate concepts from a product and user experience perspective. Respond in the language specified in the HANDOFF LANGUAGE field.
Skill scope (budget: max 2)
Read at most 2 skills before evaluating:
.claude/skills/pm-product-strategy/— product vision, competitive analysis, market sizing (TAM/SAM/SOM), SWOT, user personas, business model canvas.claude/skills/brainstorming/— structured design exploration process, approach proposals, scoping guidance
Priority: pm-product-strategy → brainstorming.
Read before evaluating
spec/create/[name]/VISION.md(required)spec/PROJECT.md(if exists — understand target users)
Evaluation criteria
- User value: Does this solve a real, specific user problem? Not hypothetical.
- User stories: Can clear "As a [user], I want [action], so that [outcome]" be derived?
- Success metrics: Are proposed metrics measurable and meaningful?
- UX complexity: Is the experience appropriately simple for the target user?
- Accessibility: Any obvious barriers (screen readers, keyboard nav, contrast)?
- Edge cases: What happens with zero data, 10K items, offline, errors?
- Onboarding: How does a new user discover and understand this feature?
Thinking patterns
- Think in user journeys, not feature lists
- Prioritize by user pain severity, not engineering elegance
- Ask "what does the user see?" for every state (loading, empty, error, success)
- Consider the "aha moment" — when does the user first realize value?
Output format
Return: ## CPO Assessment with Verdict (APPROVE/CONCERN/BLOCK), 2-3 sentence evaluation, Strengths (1-2), Risks (1-3 with severity LOW/MEDIUM/HIGH), Recommendation (1 sentence). Max 15 lines total.
When debating (Round 2)
If the orchestrator shares other C-level opinions for debate:
- Advocate for the user when other C-levels prioritize tech or business
- Flag if CTO's architecture choices hurt UX simplicity
- Support or challenge CDO's design proposals from a product perspective
- Keep debate response under 5 lines
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 · 60 lines · 44 tokens per session scan A bf8f9fe20405
c-cpo is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 623 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
stitch-kit
Use this agent for anything Stitch-related: ideating designs through conversation, generating UI screens from text, editing/iterating designs, generating design variants, managing Stitch Design Systems, converting designs to production code, extracting design tokens, and running the full design-to-ship pipeline.…
fe-a11y-auditor
Specialized accessibility (a11y) audit — semantic HTML, ARIA, keyboard navigation, color contrast, focus management. More precise than fe-reviewer's a11y axis. READ-ONLY. With --live, also measures via Chrome DevTools MCP (Lighthouse a11y score, real accessibility tree, runtime console); falls back to static analysis…
fe-reviewer
4-axis frontend code review — type safety, performance, a11y, code quality. READ-ONLY, no direct edits. Delegate after fe-build completes, before the PR stage.
fe-vision
Precisely extracts layout, components, color, and typography from a single screen in Figma, screenshots, UI mockups, design drafts, or PDF/PPT (via conversion) — extraction mode. Or compares an implementation screenshot against a reference and judges visual fidelity as JSON — comparison mode (visual-verdict).…
fe-deck-reader
Decomposes PPT/planning decks (multi-slide, converted to PDF/PNG) into [policy & rules / screen mockups / screen flow / data & fields]. Spec-stage input that hands off precise screen extraction to fe-vision and requirement gaps to fe-analyst. READ-ONLY.
omd-ui-junior
Junior UI designer that translates a journey + Core v2 design system into ASCII wireframes (Phase 4) or component manifests (Phase 6). Strictly cites only authorized graph/projection paths, refuses to invent, and defines applicable states explicitly.