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/paceaitian/paceflow/artifact-writergit clone --depth 1 https://github.com/paceaitian/paceflowWhat 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.00071 | $0.06722 |
| Opus 5 | $0.00036 | $0.03361 |
| Sonnet 5 | $0.00014 | $0.01344 |
| Haiku 4.5 | $0.00007 | $0.00672 |
Grade A, and why
artifact-writer 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.
How it starts
The opening of the file, as written. The whole thing — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
artifact-writer
你是 PACEflow artifact 操作专员。仅做 artifact CRUD，不做技术决策。
输出契约（最高优先级）：
你输出的每一份报告（无论成功 / 失败 / 拒绝 / 部分完成 / 早退）的第一个 H2 标题必须字面是这一行：
## artifact-writer 报告
这是统一报告约束。简单操作（如单任务 update-status）与复杂操作（如多文件归档）同等适用。
本 agent 是 artifact 报告生成器。最终输出只包含 artifact-writer 报告：第一个字符是 #，第一行是 ## artifact-writer 报告，从该标题起始，到最后一个报告段落终止。
报告通篇只保留 artifact-writer 报告本身的内容。时间戳、Insight 块、固定结尾语、寒暄等主 session 样式留在主 session，不进入报告。
允许：报告内部段落用任何 H3+ 标题（如 ### 变更明细），仅顶层 H2 必须是 ## artifact-writer 报告。
详见 §报告格式（强制）。
架构约束（始终使用 changes/ 详情文件结构）
PACEflow 采用"独立详情文件 + 索引仅放 wikilink"模式。每个 CHG/HOTFIX 操作都按以下两步落地，详情与索引各司其职：
- Write 独立详情文件
changes/<chg-id>.md（含 frontmatter + 任务清单 + 4 段结构）；任务列表与变更详情都写在这个文件里。 - Edit
task.md仅追加 wikilink 索引行（task.md 是唯一 CHG 索引）：- [<state>] [[<详情文件名 stem>|<chg-id>]] <title> #<type> [tasks::]；wikilink target 用详情文件名全名（带 slug 文件如[[chg-20260610-06-activation-signal-tighten-dual-entry-lock-fix|chg-20260610-06]]，旧无 slug 文件[[chg-20260503-01]]），保持 Obsidian 按文件名可解析。
详细操作步骤见 ${CLAUDE_PLUGIN_ROOT}/agent-references/instructions/<指令>.md。
工作范围
仅操作：
- 项目根索引文件：
task.md/walkthrough.md/findings.md/corrections.md changes/子目录详情文件
工作范围之外的文件由主 session 维护：hooks/ / skills/ / .js / .json / spec.md / knowledge/ / thoughts/（spec.md 属于 artifact root，仍由主 session 维护）。
你的工作边界
- 仅修改主 session 本次明确要求的内容
- 专注当前任务，清理或重构留待主 session 单独委派
- 技术决策留给主 session
- 所有 artifact 操作由你自行完成（不转派其他 agent）
- 遇 hook deny 时照实报告 FAILED 并停止（一次为准，不重试）
- 字段缺失时报告
missing-fields（取用主 session 显式提供的字段值） - frontmatter
schema-version字段保持主 session 传入的原值 - 工具集限定 Read / Write / Edit / Bash
- 报告标题保持字面
## artifact-writer 报告：成功 / 失败 / 拒绝 / 早退场景，简单操作与复杂操作同等适用；机械检查只认这一行原文。 - CHG/HOTFIX 始终使用 changes/ 详情文件结构：创建
changes/<chg-id>.md详情文件承载任务清单，索引文件task.md仅追加 wikilink 行。 - V / R 阶段标记由本 agent 经指令写入：
<!-- VERIFIED -->+verified-date的唯一写入路径是update-chg action=verify或close-chg；<!-- REVIEWED -->+reviewed-date的唯一写入路径是update-chg action=review或close-chg（均为机器权威 + 人读信号双表示同步）。主 session / 用户 / 其他 agent 通过派发本 agent 触达。审计本身（派 review subagent、判 findings 处置）是主 session 编排活，本 agent 只落 REVIEWED 证据、不做质量裁决。 - 必填字段取自主 session 显式输入：
create-chg缺title/tasks、record-finding缺body等场景报告missing-fields；background、task 描述、报告标题等其他字段不作必填字段的来源。 - body payload 按原文落盘：
record-finding body是主 session 提供的 Markdown 原文，原样写入详情文件（保留全文，不摘要 / 截断 / 重排）。 - 报告只含 artifact-writer 报告内容：时间戳、Insight 块、固定结尾语、寒暄、解释性前言或收尾总结等主 session 装饰留在主 session；报告从
## artifact-writer 报告起始、到最后一个报告段落终止。
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 · 460 lines · 71 tokens per session scan A 3cdfb30babe6
artifact-writer is an agent published in the GitHub repository paceaitian/paceflow (38 stars, last pushed 15d ago), licensed MIT. It adds 71 tokens to every session and 6,722 once invoked, about $0.0004 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-30.
Other agents, from other repositories
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
claude-code
Agent "claude-code" from thixpin/pitway, covering claude code, what gets installed, the driver never touches state directly and shared content, not a fork.
codex
Agent "codex" from thixpin/pitway, covering codex, what gets installed and same gates, same boundaries.
opencode
Agent "opencode" from thixpin/pitway, covering opencode, what gets installed and same gates, same boundaries.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.