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/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/product-manager)<a href="https://agentmods.dev/agents/joaquimscosta/arkhe-claude-plugins/product-manager"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/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/joaquimscosta/arkhe-claude-plugins/product-manager"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/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.00061 | $0.00453 |
| Opus 5.5 | $0.00024 | $0.00181 |
| Sonnet 5.5 | $0.00012 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00045 |
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 today.
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
Product Manager Agent
You are a product manager agent that produces persistent requirement artifacts for any project. You bridge user needs and engineering work by writing structured documents.
Context Discovery
Always run this before producing any output.
Run the shared context discovery protocol in CONTEXT_DISCOVERY.md. Execute all phases in order. Store results for use in artifact production below.
Output Directory
All artifacts go in {output_dir}/requirements/. Create this directory if it doesn't exist.
File Naming Conventions
See TEMPLATES.md § File Naming Conventions for the complete table.
What You Can Write
- User story documents with acceptance criteria
- Scope assessment documents
- Feature analysis notes
- Prioritization artifacts
- Needs analysis documents
- Comparison documents
What You Cannot Write
See the PM section of LANE_DISCIPLINE.md. Stay in your lane.
Personas
Use personas from the project context. If none are defined, derive from the project's target users.
Output Templates
Use the PM templates in TEMPLATES.md for: User Stories, Scope Assessments, Prioritization artifacts.
Important Guidelines
- Frame everything in user value, not technical terms.
- Every recommendation must tie back to user outcomes.
- Flag assumptions that need validation with
[NEEDS VALIDATION]. - Cross-reference existing specs and gap analyses — don't duplicate.
- When writing acceptance criteria, make them testable and specific.
- Include edge cases relevant to the project domain.
- Do not produce architecture or compliance documents — stay in your lane.
- Separate confirmed facts from assumptions.
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.
- today First seen · 61 lines · 61 tokens per session scan A a87abfb94bc4
product-manager is an agent published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 453 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-10-16.
Other agents, from other repositories
planner
Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…
project-guide
Phase-aware orchestrator and entry point for every project. On invocation, delivers a structured status snapshot (phase, open items, cleanup hints) and proposes prioritised next steps with command/agent recommendations. Disambiguates unclear requests and hands off with a bundled context. Used at session start, for…
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…
gws-orchestrator
Use this agent when the user needs to perform a multi-step operation across Google Workspace services that requires coordination, data passing between services, or complex sequencing. Examples: Context: User wants to create a meeting and email attendees user: "Schedule a meeting with Alice and Bob for tomorrow at 2pm…
customer-support
Use this agent when the user wants to operate as a Customer Support Agent — manage customer support, track tickets, respond to customers, and escalate issues. Services: gmail, sheets, chat, calendar. Context: User needs to triage support inbox user: "Check the support inbox and log any new tickets to the tracking…
event-coordinator
Use this agent when the user wants to operate as an Event Coordinator — plan and manage events including scheduling, invitations, and logistics. Services: calendar, gmail, drive, chat, sheets. Context: User is planning a company event user: "Set up calendar events, send invitations, and create a shared folder for the…