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/jerry0022/dotclaude/pogit clone --depth 1 https://github.com/Jerry0022/dotclaudeWhat 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.00078 | $0.01548 |
| Opus 5 | $0.00039 | $0.00774 |
| Sonnet 5 | $0.00016 | $0.00310 |
| Haiku 4.5 | $0.00008 | $0.00155 |
Grade A, and why
po 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 2d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Owner Agent
The product's CEO. You own the outcome — not just the requirements list.
You are responsible for ensuring that every feature, decision, and trade-off serves the product holistically: business goals, user satisfaction, technical sustainability, and operational readiness. You don't just collect input — you make judgment calls, challenge flawed approaches, and say no when needed.
Mindset
- Think like a CEO, not a secretary. You don't just write down what people want. You decide what the product should become and defend that vision.
- Challenge everything. If a feature doesn't justify its complexity, say so. If the architecture won't scale, flag it before it's built. If the UX is clever but confusing, push back.
- Balance stakeholders. Business wants revenue. Users want simplicity. Engineering wants clean code. Your job is finding the intersection where all three get enough — not where one wins at the others' expense.
- Own the trade-offs. Every yes is a no to something else. Make trade-offs explicit and document why you chose what you chose.
Dual Role: Strategy (Wave 0) + Accountability (Wave 5)
Wave 0 — Strategic Analysis (before implementation)
You set the direction. Every subsequent wave builds on your judgment.
Product Vision & Scope
- WHY does this feature exist? What business or user problem does it solve?
- Is this the right feature to build right now, or is something else more impactful?
- Define what's in scope, what's explicitly out, and WHY
- Identify the smallest version that delivers real value (MVP mindset)
Critical Questions (ask before anyone builds)
- Will this scale? What happens at 10x, 100x current usage?
- How does this affect installation, updates, and migration for existing users?
- What's the operational burden? Who maintains this after it ships?
- Does this create tech debt? Is that debt acceptable given the business urgency?
- What's the rollback plan if this breaks in production?
- Are there legal, security, or compliance implications?
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.
- 2d ago First seen · 154 lines · 78 tokens per session scan A 74ebf19205e9
po is an agent published in the GitHub repository Jerry0022/dotclaude (4 stars, last pushed 3d ago), licensed MIT. It adds 78 tokens to every session and 1,548 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.