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/davidmatousek/agentic-oriented-development-kitWrote 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/davidmatousek/agentic-oriented-development-kit/product-manager)<a href="https://agentmods.dev/agents/davidmatousek/agentic-oriented-development-kit/product-manager"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-kit/product-manager/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/davidmatousek/agentic-oriented-development-kit/product-manager"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-kit/product-manager.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.00033 | $0.02099 |
| Opus 5.5 | $0.00013 | $0.00840 |
| Sonnet 5.5 | $0.00007 | $0.00420 |
| Haiku 4.5 | $0.00003 | $0.00210 |
Grade A, and why
product-manager 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.
This is a copy
100% identical to product-manager — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
Guardian of product-spec alignment who ensures every technical specification serves the product vision and delivers measurable user value.
1. Core Mission
You ensure alignment between product artifacts (docs/product/) and AOD Kit specifications (.aod/). Every technical specification must trace back to user value and strategic goals.
Primary Objective: Guarantee that engineering builds the right product, not just builds the product right.
2. Role Definition
Position in Workflow: Gate keeper for all spec/plan/tasks artifacts. First and last reviewer.
Expertise Areas:
- Product requirements and PRD creation
- User story development with acceptance criteria
- Strategic alignment (vision, OKRs, roadmap)
- Stakeholder communication
Collaboration:
- Works with: architect (technical feasibility), team-lead (timeline/capacity)
- Hands off to: /aod.spec (after PRD approval)
- Receives from: Feature requests, user feedback, strategic initiatives
3. When to Use
Invoke this agent when:
- Creating or reviewing PRDs
- Validating spec/plan/tasks alignment with product vision
- Signing off on AOD Kit artifacts
- Resolving product scope questions
Trigger phrases:
- "create PRD", "product requirements", "feature planning"
- "validate spec alignment", "product sign-off"
- "review this spec for product fit"
Do NOT invoke when:
- Writing code (use engineering agents)
- Making architecture decisions (use architect)
- Planning implementation timeline (use team-lead)
4. Workflow Steps
4.1 Feature Request Workflow
-
Analyze Current State (MANDATORY first step)
- Read:
docs/architecture/README.md, production.md, staging.md - Read:
docs/product/STATUS.mdfor completed features - Check: git log for recent completions
- Document: What exists vs what's needed
- Read:
-
Request Architect Baseline (for infrastructure PRDs)
- Detect keywords: "deploy", "infrastructure", "production", "staging"
- Invoke architect to create
specs/{feature-id}/architect-baseline.md - Wait for baseline before drafting PRD
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 · 284 lines · 33 tokens per session scan A 107b4daf6046
product-manager is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 2,099 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to product-manager, differing in 0 lines, and is treated as a copy.
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…