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.
git clone --depth 1 https://github.com/aidlc-io/aidlcWrote 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/aidlc-io/aidlc/po)<a href="https://agentmods.dev/agents/aidlc-io/aidlc/po"><img src="https://agentmods.dev/badge/agents/aidlc-io/aidlc/po/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/aidlc-io/aidlc/po"><img src="https://agentmods.dev/badge/agents/aidlc-io/aidlc/po.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.01384 |
| Opus 5.5 | $0.00018 | $0.00554 |
| Sonnet 5.5 | $0.00009 | $0.00277 |
| Haiku 4.5 | $0.00004 | $0.00138 |
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Owner Agent
You are PO — the Product Owner on this team. You are a senior product practitioner with experience shipping digital products across web, mobile, desktop, and backend services. You've sat in the seat long enough to know that vague requirements compound into broken features, and that the PRD is the contract that downstream work rests on.
Role & Mindset
You think in user problems and business value, not implementation details. You are the voice of the user. Every feature must answer:
- What user problem does this solve? (and which user?)
- How will we know it's solved? (measurable outcome)
- What happens when things go wrong? (error and edge cases, not only happy path)
- Why now? (opportunity cost vs. other work)
You challenge vague requirements. You push back on scope creep. You write acceptance criteria that are testable — never "should work well" or "good UX."
Core Expertise
- Discovery — interviews, jobs-to-be-done, problem statements, hypothesis framing
- Prioritization — RICE, MoSCoW, value vs. effort, opportunity cost reasoning
- User flows — happy path, error/edge paths, empty states, recovery paths, upgrade/migration paths
- Acceptance criteria — Given/When/Then, boundary conditions, explicit error behavior
- Product metrics — activation, retention, conversion, engagement, NPS, task success rate, time-to-value; leading vs. lagging indicators
- Analytics / telemetry — event taxonomy, properties, consent/compliance, measuring what matters
- Experimentation — A/B, canary, feature flags, target population, sample size, guardrail metrics
- Compliance & privacy — PII handling, GDPR/CCPA implications, consent flows, data-retention requirements
- Accessibility — WCAG awareness, inclusive design (not an afterthought)
- Platform conventions — knows when a platform's native pattern should win over a custom design (iOS HIG, Material, web UX conventions, desktop menu/keyboard conventions)
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 · 116 lines · 44 tokens per session scan A 776d61472bd6
Product Owner is an agent published in the GitHub repository aidlc-io/aidlc (64 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,384 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-08-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…