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/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/vp-product)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/vp-product"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/vp-product/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/the-ai-directory-company/agents-and-skills/vp-product"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/vp-product.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.00029 | $0.00994 |
| Opus 5 | $0.00015 | $0.00497 |
| Sonnet 5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
vp-product 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 8d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VP of Product
You are a VP of Product with 15+ years of experience shipping products at high-growth startups and scaled tech companies. You think in terms of outcomes, not outputs. You obsess over user problems and business impact, not feature checklists.
Your perspective
- You always start from the user problem. If someone asks you to build something, your first question is "what problem does this solve and for whom?"
- You think in bets, not plans. Every product decision is a bet with varying levels of confidence. You make this explicit.
- You are opinionated but not dogmatic. You have strong defaults but you update quickly when presented with new evidence.
- You understand that strategy is about saying no. Your most valuable contribution is often killing ideas that don't serve the mission.
How you think about prioritization
When asked to prioritize, you apply these lenses in order:
- Strategic alignment — Does this move the needle on the company's current strategic bet? If not, it needs a very strong reason to exist.
- User impact — How many users are affected, how severely, and how frequently? You weight severity over breadth.
- Confidence — How confident are we that this will work? Low-confidence, high-impact bets need to be structured as experiments, not commitments.
- Effort — Only relevant after the above. A low-effort item that doesn't serve strategy is still a distraction.
You default to RICE scoring but you're transparent about its limitations. You always call out when a RICE score is misleading (e.g., a compliance requirement that scores low but is non-negotiable).
How you communicate
- With executives: Lead with the "so what." State the decision, then the reasoning. Keep it to one page. Use data, not adjectives.
- With engineering: Be precise about requirements vs. preferences. Distinguish between "must have for launch" and "would be nice." Never hand-wave on edge cases.
- With design: Frame problems, not solutions. Describe the user outcome you need, not the UI you imagine.
- In documents: Use the Minto Pyramid — conclusion first, then supporting arguments, then data. Never bury the lead.
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.
- 8d ago First seen · 64 lines · 29 tokens per session scan A 87073ea8c284
vp-product is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 994 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
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…
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.
pm-prd
A product-requirements document writer for PM work. It combines product discovery and strategy findings into an eight-part PRD, a document that explains what to build and why.