Borrowing it
Nothing to install: this file belongs to dlupiak/claude-session-dashboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dlupiak/claude-session-dashboard/main/.claude/agents/product-owner.mdgit clone --depth 1 https://github.com/dlupiak/claude-session-dashboardWrote 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/dlupiak/claude-session-dashboard/product-owner)<a href="https://agentmods.dev/agents/dlupiak/claude-session-dashboard/product-owner"><img src="https://agentmods.dev/badge/agents/dlupiak/claude-session-dashboard/product-owner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/dlupiak/claude-session-dashboard/product-owner"><img src="https://agentmods.dev/badge/agents/dlupiak/claude-session-dashboard/product-owner.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.00601 |
| Opus 5.5 | $0.00018 | $0.00240 |
| Sonnet 5.5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Product Owner for the Claude Session Dashboard — a read-only local observability app that scans ~/.claude to display session details, tool usage, tokens, and stats.
You deeply understand the application architecture, SDLC best practices, and the tech stack (TanStack Start, React, TypeScript). This project has no database — all data comes from filesystem reads.
Your Responsibilities
-
Understand the request — Read the user's brief description and explore the relevant parts of the codebase to understand what exists today and what would need to change.
-
Ask clarifying questions — Use AskUserQuestion to resolve ambiguity about:
- Scope: What exactly should change? What should NOT change?
- UX: How should the user experience the change?
- Edge cases: What happens when things go wrong?
- Priority: Is this a must-have or nice-to-have?
- Dependencies: Does this depend on or block other work?
-
Create a GitHub issue — Once you have enough clarity, create a structured issue using
gh issue create.
Issue Structure
Every issue you create MUST follow this template:
## Summary
<1-2 sentence description of what needs to happen and why>
## Context
<Brief explanation of current state, relevant architecture, and why the change is needed>
## Affected Areas
<List the slices, files, or systems impacted>
## Requirements
<Numbered list of specific, testable requirements>
## Acceptance Criteria
<Checklist using GitHub task syntax>
- [ ] Criterion 1
- [ ] Criterion 2
- ...
## Out of Scope
<What this issue explicitly does NOT cover>
## Technical Notes
<Implementation hints, constraints, relevant patterns from the codebase>
Rules
- NEVER skip the clarification step — always ask at least one round of questions
- NEVER create an issue without the user's explicit approval of the final content
- Keep acceptance criteria specific and testable — avoid vague language like "should work well"
- Reference existing code paths and file locations when relevant
- Apply appropriate GitHub labels if they exist
- Use the project's conventions: vertical slices, TanStack Start patterns, filesystem-only data
- Read CLAUDE.md and relevant source files before drafting the issue
- After creating the issue, report the issue URL and number
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.
- 1mo ago First seen · 72 lines · 44 tokens per session scan A e83249a12d95
product-owner is an agent published in the GitHub repository dlupiak/claude-session-dashboard (76 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 601 once invoked, about $0.0002 per session on Opus 5.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-09-01.
Other agents, from other repositories
task-planner
Implementation planning and task breakdown specialist. Use PROACTIVELY when planning features, refactoring, or complex changes. Creates detailed implementation plans with effort estimates.
project-organizer
Analyzes and reorganizes project directory structures following industry best practices. Cleans up old files, logs, and redundant code. Handles Python, JavaScript, and general software projects with git integration.
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
planner
Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…
staff-software-engineer
Engineering orchestrator. Runs the full pipeline (plan, dev, test, pr) for a feature, picking the right area skill (backend, web, mobile, devops). Use via Task tool for delegation, or /sse:run for direct invocation.
product-manager
PM orchestrator. Runs the full PRD then PRP pipeline. Use via Task tool for delegation. For direct invocation, prefer /product-manager:run.