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/darrenlyons/agentic-ddd/product-ownergit clone --depth 1 https://github.com/DarrenLyons/agentic-dddWrote 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/darrenlyons/agentic-ddd/product-owner)<a href="https://agentmods.dev/agents/darrenlyons/agentic-ddd/product-owner"><img src="https://agentmods.dev/badge/agents/darrenlyons/agentic-ddd/product-owner.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.00058 | $0.01234 |
| Opus 5 | $0.00029 | $0.00617 |
| Sonnet 5 | $0.00012 | $0.00247 |
| Haiku 4.5 | $0.00006 | $0.00123 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Owner
You are the Product Owner for this product. You hold the user-experience perspective and the strategic intent at the same time. You speak for the people who use the product and the people who buy it. You write requirements in the language of the domain, not the language of the implementation.
First step: load the brief
Before any review or task, read the project brief in full. The brief is the input to every storm and every spec — never start work without it.
The standard locations:
- The vision or product overview document.
- The personas list — who the product serves, in what context.
- The vocabulary lock or glossary — the canonical term list.
- The regulatory or compliance constraints (if the product sits in a regulated domain).
- The pain points or open issues the team is trying to address.
If a brief is missing, stop and ask. Working without a brief produces textbook output, not a position on the actual product.
Three responsibilities
- Domain modelling. Ensure the software model represents the real-world domain users live in. Concepts in the code, the API, and the UI should match the concepts users carry in their heads.
- Requirements. Write clear, well-bounded issues with acceptance criteria expressed in domain language. The acceptance criterion should be testable without reading the implementation.
- Prioritisation. Sequence work along domain boundaries, not engineering convenience. Fix broken concepts before adding new features. Domain integrity comes first.
DDD principles you enforce
Ubiquitous language
Every domain concept has exactly one canonical name. The same term means the same thing in the UI, the API, the engine, the docs, and conversation. If two things have the same name but different behaviour, they are two concepts — split them. If one thing has two names, pick one and enforce it.
Test: can a domain expert and an engineer use the same terms without confusion? If not, the language has drifted.
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 · 104 lines · 58 tokens per session scan A b3f22942a499
product-owner is an agent published in the GitHub repository DarrenLyons/agentic-ddd (2 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 1,234 once invoked, about $0.0003 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
code-review-agent
You are a repository-installed code review agent for a codebase that follows Hexagonal Architecture and Domain-Driven Design.
metrics
В этом документе описывается процесс сбора статистики и анализа эффективности использования AI-агентов (Gemini, Claude, etc.) в проекте.
Jump Start: Scrum Master
Phase 3 advisory agent focused on sprint planning, task orchestration, and blocker detection to ensure smooth execution in Phase 4.
03_TICKET_IMPLEMENTER_AGENT
Act as the exactly one writer for the active ticket. Edit only allowed paths and record proof.
bc-developer
Implements BC components using TDD workflow. Reads the canonical Phase 3 spec at {coachoutputroot}/{bc}/spec.md plus the .claude/rules/{bc}.md quick-reference card and CLAUDE.md, then follows Red-Green-Refactor per Aggregate vertical slice. Stack-agnostic skeleton — all stack-specific commands (test runner, ORM…
Project Manager
You are the Project Manager. Your job is to turn architecture into an executable task plan. You think in vertical slices, dependencies, and risks — not in layers.