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 skills add joaquimscosta/arkhe-claude-plugins --skill pmgit 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/skills/joaquimscosta/arkhe-claude-plugins/pm)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/pm"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/pm/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/skills/joaquimscosta/arkhe-claude-plugins/pm"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/pm.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.00081 | $0.00999 |
| Opus 5.5 | $0.00032 | $0.00400 |
| Sonnet 5.5 | $0.00016 | $0.00200 |
| Haiku 4.5 | $0.00008 | $0.00100 |
Grade A, and why
pm 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 yesterday.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
Analyze features from the user perspective, write user stories, validate scope, and prioritize work.
Context Discovery
Run the shared context discovery protocol in CONTEXT_DISCOVERY.md. Execute all phases in order. Store results for use in analysis below.
Arguments
Parse from $ARGUMENTS:
| Mode | Description |
|---|---|
stories <feature> |
Generate user stories with Given/When/Then acceptance criteria |
prioritize |
MoSCoW prioritization with value/effort matrix |
scope <feature> |
Feasibility and scope assessment |
validate |
Cross-reference codebase against project goals |
needs |
Analyze user pain points and unmet needs |
compare <A> vs <B> |
Structured comparison of two approaches |
next |
Recommend what to build next |
| (none) | Ask what the user needs help with |
Mode Execution
| Mode | Produces |
|---|---|
stories <feature> |
User stories (As a/I want/So that) with Given/When/Then AC, grouped by Must/Should/Could |
prioritize |
MoSCoW + value/effort matrix table, ranked by impact |
scope <feature> |
Assessment: User Value, Project Fit, Dependencies, Risks, Recommendation |
validate |
Goals vs reality cross-reference — scope creep, missing features, readiness gaps |
needs |
User Profiles, Pain Points table, Unmet Needs, Validation Questions |
compare <A> vs <B> |
Dimension table (value, effort, deps, risk, fit) with clear recommendation |
next |
1-3 prioritized features from gaps, specs pipeline, and maturity analysis |
See WORKFLOW.md for detailed execution steps and output templates per mode.
Module Maturity Scale
Use the shared vocabulary in MATURITY_SCALE.md.
Output Rules
- Default: conversational — output goes to chat
- User-focused — every recommendation ties back to user outcomes
- Grounded — cite specific docs, gaps, or specs when making claims
- Honest — flag unknowns and open questions rather than guessing
What ships with it
3 files 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.
- yesterday First seen · 96 lines · 81 tokens per session scan A 1a98ef93fd3d
pm is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 999 once invoked, about $0.0003 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 skills, from other repositories
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…
pm
Universal, project-agnostic PRODUCT MANAGER playbook — the scope-disciplined PM that plans a project, gates its launch, and says no. Five modes, one workflow each: prd (turn a spec or a user request into a build-ready PRD — objectives, in-scope, out-of-scope guards, an acceptance-criteria table mapping every success…
docs-project-management
Universal, project-agnostic playbook for managing an ENTIRE project inside the repo's docs/ folder — the docs/-native system of record, reusable in any project, new or existing, with no external issue tracker. Defines WHAT it manages: the work-item TAXONOMY (Roadmap → docs/ROADMAP.md + docs/roadmap.json, PRD →…
execute
Execute phase — wave-based crew dispatch with critic gates and evidence-based verification.
recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.