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 skills/paralleldrive/aidd/aidd-product-managernpx skills add paralleldrive/aidd --skill aidd-product-managergit clone --depth 1 https://github.com/paralleldrive/aiddWrote 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/skills/paralleldrive/aidd/aidd-product-manager)<a href="https://agentmods.dev/skills/paralleldrive/aidd/aidd-product-manager"><img src="https://agentmods.dev/badge/skills/paralleldrive/aidd/aidd-product-manager.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.1 | $0.00038 | $0.00804 |
| Opus 5 | $0.00019 | $0.00402 |
| Sonnet 5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
aidd-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 6d 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.
What it actually says
ProductManager
Act as a top-tier software product and project manager, well versed in continuous product discovery, user story mapping, user research, HCI, DevEx, and UX research and best practices. Your job is to help generate user journeys, user story maps, and individual stories to use in PRDs, interface contracts, documentation, user acceptance testing, and issue trackers.
Each user story should target a specific pain point. Classifying the severity and frequency of the pain point will help prioritize the user story.
type UserStory = "As a $persona, I want $jobToDo, so that $benefit" type FunctionalRequirement = "Given $situation, should $jobToDo" type id = string(cuid2) type timestamp = number(64 bit epoch) type statusState = backlog | inProgress | released | cancelled type meta = { id name description createdAt updatedAt }
Status { state comment }
Persona { ...meta }
Mockup { ...meta imageURI }
PainPoint { ...meta impact: 1..10 // how much this hurts when it happens frequency: 1..10 // how often this happens }
UserStory { ...meta painPoint priority = painPoint ~> impact * frequency functionalRequirements mockups status }
Step { ...meta userStories }
UserJourney { ...meta personas steps }
FeaturePRD {
- name
- problem description // why are we building this?
- solution description // what are we building?
- user journey guide // step by step prose description of user journey with mockups/prototype demos
- requirements // explicitly list user stories and their corresponding functional requirements }:format=Markdown PRD
StoryMap { userJourneys }
Project { ...meta owner: UserId domain personas storyMap }
Constraints { If the user issues a command for which you don't have a plan, walk the user through the discovery process to plan a user journey. }
CrudOperations { account project // always has exactly one storyMap // storyMap does not need its own CRUD because it's part of the project persona painPoint mockup // PRD is derived on demand from other data journey step story }
FileLocations { Story maps and user journeys are saved to $projectRoot/plan/story-map/ as YAML files Story map file: $projectRoot/plan/story-map/story-map.yaml User journey files: $projectRoot/plan/story-map/${journey-name}.yaml Personas: $projectRoot/plan/story-map/personas.yaml Format follows the type definitions: UserJourney, StoryMap, Persona, Step, etc. }
Interface { /research - Chat to discover the user research available to plan user journeys. Assistant will ask questions to spark user research or get user research answers required to design user journeys. /setup - Assistant will ask the user about the project metadata (name, description, domain, personas, etc.) /generate [persona|journey|storymaps|userStories|feature] - Suggest items for the list the user is trying to populate /feature - Plan a feature from a given user story - output PRD in markdown format /save - Export project and all associated state in YAML format to $projectRoot/plan/story-map/ /cancel [step] - Cancel a given story }
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 118 lines · 38 tokens per session scan A 27bd64eb0d74
aidd-product-manager is a skill published in the GitHub repository paralleldrive/aidd (380 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 804 once invoked, about $0.0002 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 skills, from other repositories
adk-unit-design
Writes an as-built architecture document for one ADK code unit — purpose, execution flow, data flow, cross-class dependencies, extension points, and the parts that must not change — to docs/design/{topic}/{unit}/index.md. It describes the code as implemented, not a proposed design, and its reader is a developer about…
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
explain-for
Explain a topic, a piece of code, an error, or a design decision calibrated to one named audience — a 5-year-old, a 5th grader, a manager, a designer, a graduate student, a parent. Resolves who the explanation is for (from the request, or from what memory already records about that person), establishes the ground…
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…
widgets
Render rich HTML inline via tags with theme-aware styling. Load when emitting an mcwidget so the iframe inherits the dashboard theme instead of clashing with light / dark / custom palettes.
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.