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 agents/arch3rpro/ark-space/prd-plannergit clone --depth 1 https://github.com/arch3rPro/ark-spaceWhat 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 | $0.00018 | $0.00248 |
| Opus 5 | $0.00009 | $0.00124 |
| Sonnet 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 2d 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.
- 2d 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 7d ago), licensed MIT. It adds 18 tokens to every session and 248 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-08-31.
Other agents, from other repositories
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
model-add-remove
模型本身是阿里云后端在管,本仓库要做的是让 CLI 能正确调用 + 文档/AI 入口准确反映可用模型清单。.
frontend-design
React 前端技术设计专家。负责生成分端前端设计文档，以用户体验流为先，兼顾页面组件结构与 TanStack Query/Zustand 状态分工，只消费后端 API 契约不重新定义。.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.