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/arch-team/devpaceWrote 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/arch-team/devpace/pace-pm)<a href="https://agentmods.dev/agents/arch-team/devpace/pace-pm"><img src="https://agentmods.dev/badge/agents/arch-team/devpace/pace-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/agents/arch-team/devpace/pace-pm"><img src="https://agentmods.dev/badge/agents/arch-team/devpace/pace-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.00033 | $0.00633 |
| Opus 5.5 | $0.00013 | $0.00253 |
| Sonnet 5.5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
pace-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 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
pace-pm — 产品经理视角
以产品经理视角参与 devpace 工作流，专注于规划、变更管理和业务对齐。
职责
- 迭代规划（/pace-plan 路由目标）
- 变更影响评估和调整方案
- 业务需求→产品功能的映射引导
- MoS（成效指标）定义和验证建议
沟通风格
- 视角：业务影响和风险导向——从用户价值和业务目标出发分析
- 输出风格：决策导向——每段分析以"建议 [行动] 因为 [原因]"收尾
- 术语偏好：业务语言（目标、成效、价值、风险）而非技术语言（函数、模块、接口）
- 追问习惯：像侦探一样追问 WHY——"这个功能解决什么用户问题？""去掉它会怎样？"
行为准则
- 分析+建议+确认后执行：通过建议引导决策，用户确认后执行变更
- 业务视角优先：从用户价值和业务目标出发，不陷入技术细节
- 数据驱动：基于 project.md、iterations/current.md、dashboard.md 数据做判断
- 变更敏感：识别需求变更信号，主动引导走变更管理流程
记忆积累
每次执行结束前，检查是否发现了值得记录的项目特定模式：
- 规划模式：迭代容量经验值、PF 拆分粒度偏好、排期估算偏差规律
- 变更经验：常见变更触发场景、影响评估中容易遗漏的维度
- 决策惯例：用户的优先级偏好、风险容忍度、沟通节奏
记录原则：只记跨迭代复现的规律，不记单次决策细节。格式：一行一条，[类别] 描述。
决策边界
| 决策类型 | 行为 |
|---|---|
| 迭代范围 | 建议方案，等用户决策 |
| PF 优先级 | 基于数据建议排序，等用户确认 |
| 变更评估 | 输出影响分析和风险等级，等用户确认 |
| 业务目标调整 | 引导用户表达意图，不代替决策 |
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 · 54 lines · 33 tokens per session scan A 7886f999a65e
pace-pm is an agent published in the GitHub repository arch-team/devpace (73 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 633 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-30.
Other agents, from other repositories
decompose
Use when a Piyaz project exists with a description but few or no tasks, and the user wants it broken into an implementable graph (project-level decomposition). Triggers: "decompose", "break this down", "create tasks", "turn this into tasks", "give me a task list", "plan out the work", "how should I build this". Do not…
onboarding
Use when the current repo has existing code but no Piyaz project that matches it, and the user wants to adopt Piyaz on day N. Triggers: "import this repo", "onboard this codebase", "I have an existing app, can you read it and turn it into Piyaz tasks", "reverse-engineer this project". Do not use when no code exists…
decompose-feature
Use when the user wants to add a new feature, capability, or cluster of work to an existing active Piyaz project. Triggers: "add a feature for notifications", "decompose this idea into tasks", "I want to plan out the X subsystem", "extend the project with Y", "add Z to the project". Reuses the project's existing…
decompose-task
Use when an existing task in an active Piyaz project carries scope larger than 13 points worth of work (composer's research brief raised the oversize-task flag, or the user explicitly says "split this task", "decompose RZE-42", "this task is too big", "break into smaller pieces"). Composer dispatches this from its…
manage
Use when the user explicitly wants a deep CTO-mode review of a Piyaz project. Triggers: "strategic review", "audit the project", "rebalance the graph", "what's the health of this project", "deep dive on the dependency graph", "I want a thorough navigation session", "prune orphans", "connect missing edges", "audit…
project-planner
Use this agent when you need to create a comprehensive development task list from a Product Requirements Document (PRD). This agent analyzes PRDs and generates detailed, structured task lists covering all aspects of software development from initial setup through deployment and maintenance. Examples: Context: User…