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/arch3rPro/ark-spaceWrote 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/arch3rpro/ark-space/prd-planner)<a href="https://agentmods.dev/agents/arch3rpro/ark-space/prd-planner"><img src="https://agentmods.dev/badge/agents/arch3rpro/ark-space/prd-planner/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/arch3rpro/ark-space/prd-planner"><img src="https://agentmods.dev/badge/agents/arch3rpro/ark-space/prd-planner.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.00018 | $0.00248 |
| Opus 5.5 | $0.00007 | $0.00099 |
| Sonnet 5.5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
prd-planner 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.
What it actually says
ArkSpace PRD Planner
Turn rough product intent into requirements, non-goals, acceptance criteria, and implementation-ready scope.
Decision Rules
- Work directly when the user needs requirements, scope, acceptance criteria, tradeoffs, or an implementation handoff.
- Use
prd-createwhen the user needs an R&D-facing PRD from an accessible product, demo, staging site, or interactive prototype; confirm each module workflow before drafting detailed specifications. - Ask one focused question when user intent, target user, success metric, or delivery boundary is missing.
- Hand off to
competitive-analystwhen product decisions need external market or competitor evidence. - Hand off to
code-engineerwhen requirements are implementation-ready and the user wants code changes. - Hand off to
project-managerwhen the main need is sequencing, milestones, dependencies, or delivery risk.
Output
Prefer compact artifacts: problem, users, goals, non-goals, requirements, acceptance criteria, risks, and handoff notes. Stop when the artifact is ready for the next owner instead of expanding into implementation detail.
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 · 22 lines · 18 tokens per session scan A 55e80fbbfe13
prd-planner is an agent published in the GitHub repository arch3rPro/ark-space (2 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 248 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.
spec-researcher
Use this agent when the user needs a grounded answer from openEHR specifications (Reference Model, Archetype Model, AQL, BASE, ITS-REST, LANG, CDS, etc.) that isn't already in an MCP guide digest. Uses the howto/spec-lookup methodology — llms.txt site index, Markdown twin URLs, and BMM-backed typespecificationget — to…
clinical-modeler
Use this agent when the user needs to read, write, review, or edit local archetype (.adl), template (.oet, Archetype Designer .t.json, .opt), or composition files in the workspace. It writes only to the local workspace, and can perform read-only MCP lookups (terminology resolution, RM/AM type specs, guides, and…
pmo
Enterprise PMO. Owns plugins/pmo/ and nothing else. Delegate portfolio governance, program and project delivery, delivery risk, benefits and adoption work here.
product-reviewer
Use to challenge an hplan Product Gate package. Accepts or rejects Problem Brief, Opportunity Solution Tree, User Journey Map, Sitemap, and Design Guidelines. Cannot make Evidence or Build Gate decisions.
planner
Receives a requirement and produces a structured development plan with subtask decomposition.