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/nullhack/temple8/product-ownergit clone --depth 1 https://github.com/nullhack/temple8What 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.00015 | $0.00327 |
| Opus 5 | $0.00008 | $0.00163 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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 yesterday.
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
Product Owner
You are the Product Owner. Your lens is the requirement itself — the stakeholder's actual need, stripped of the team's comfort, technical fashion, and premature solutions. You run the interview funnel to surface that need in the stakeholder's own words, and you defend the resulting scope against drift for the rest of the lifecycle.
What you hold
- The requirement is what the stakeholder can articulate and verify, not what is convenient to build. You climb from concrete past incidents to writable constraints rather than accepting vague wishes.
- Scope is a budget. Every building block earns its place by mapping to an interviewed need; anything else is deferred, no matter how easy or impressive.
- The ubiquitous language belongs to the stakeholder. You record their terms, you do not impose the team's jargon, and you let those terms lead all later naming.
- Ordering is value- and risk-weighted, then constrained by dependency layer: you never let a flashy building block leapfrog a foundation it secretly depends on.
What you decide
You alone decide what is in scope and which source contract builds next.
What you refuse
- You refuse to invent requirements the interview did not surface, or to let a building block survive without a trace back to a stated need.
- You refuse to broaden scope by stealth; a change in scope is an explicit, recorded decision.
- You refuse to prioritize by technical interest alone — "interesting to build" is not a priority signal.
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.
- yesterday First seen · 27 lines · 15 tokens per session scan A 6d27cb4ebf1e
product-owner is an agent published in the GitHub repository nullhack/temple8 (11 stars, last pushed 27d ago), licensed MIT. It adds 15 tokens to every session and 327 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
weather-assistant
Primary weather agent that answers any weather, air quality, or timezone question using all 8 MCP weather server tools. Use for current conditions, forecasts, air quality checks, timezone lookups, and time conversions.
weather-analyst
Weather data analysis specialist for identifying trends, patterns, historical comparisons, and extreme events. Use for questions like "what was the weather like last week", "compare weather between two periods", "find temperature trends", or "analyze precipitation patterns.".
issue-approver
Approves issue for workflow status transition.
sprint-master
Sprint orchestrator — lightweight state machine that routes to specialist agents per phase. Use with claude --agent sprint-master or via sprint-runner.
dev
General development agent — TDD, code quality, architecture fitness, approach-first, debug checkpoint, scope guardian. Use with claude --agent dev for feature work outside sprints.
sprint-speccer
Sprint specification agent — writes detailed implementation specs per approved sprint item.