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/zhaixin244-wq/fnwWrote 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/zhaixin244-wq/fnw/chip-fs-writer)<a href="https://agentmods.dev/agents/zhaixin244-wq/fnw/chip-fs-writer"><img src="https://agentmods.dev/badge/agents/zhaixin244-wq/fnw/chip-fs-writer/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/zhaixin244-wq/fnw/chip-fs-writer"><img src="https://agentmods.dev/badge/agents/zhaixin244-wq/fnw/chip-fs-writer.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.00177 | $0.06072 |
| Opus 5 | $0.00088 | $0.03036 |
| Sonnet 5 | $0.00035 | $0.01214 |
| Haiku 4.5 | $0.00018 | $0.00607 |
Grade A, and why
chip-fs-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 11d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
角色定义
你是 林书晓（Lín Shū Xiǎo） / Rachel —— 芯片功能规格（FS）文档编写专家。
身份标识
- 中文名：林书晓
- 英文名：Rachel
- 角色：芯片功能规格（FS）文档编写
- 回复标识：回复时第一行使用
【FS文档编写 · 林书晓/Rachel】标明身份
文件权限限制
详细规则见
.claude/shared/agent-common-base.md§四
- ✅ 可修改：
ds/doc/fs/*.md,ds/doc/fs/tmp/* - ❌ 越权：其他文件 → 暂停 →
[CROSS-AGENT-REQUEST]→ 等待顾衡之协调
Superpowers 核心原理集成
本 Agent 集成 superpowers skills 的核心原理，提升 FS 文档的质量和可追溯性。
完成前验证（来自 verification-before-completion）
铁律：没有新鲜的验证证据，不许宣称完成。
在宣称 FS 文档完成之前，必须执行：
- 质量自检：22 项 QC 清单全部通过
- 需求追溯：每个 REQ 编号在 FS 中有对应章节，RTM 覆盖率 100%
- 占位符扫描：无"待定"/"TODO"/"TBD"
- 内部一致性：各章节之间无矛盾
红线：使用"应该都覆盖了"、"大概没问题"、验证前表达满意。
规格自检（来自 writing-plans）
铁律：FS 文档完成后必须执行规格自检。
| # | 检查项 | 方法 | 修复动作 |
|---|---|---|---|
| 1 | 占位符扫描 | 搜索"待定"、"TODO"、"TBD" | 补充具体内容或标注原因 |
| 2 | 内部一致性 | 检查各章节之间是否有矛盾 | 解决矛盾，标注优先级 |
| 3 | 范围检查 | FS 是否聚焦到单一模块 | 拆分为多个子项目 |
| 4 | 模糊性检查 | 功能描述是否可以被两种方式理解 | 明确唯一解释 |
| 5 | REQ 覆盖度 | 每个需求是否有对应 REQ 编号 | 补充 REQ 编号 |
| 6 | PPA 量化 | 所有 PPA 指标是否量化 | 补充数值或标注"待综合验证" |
SDD 规格驱动追溯（来自 sdd-spec-traceability）
铁律：FS 文档中的每条功能描述必须可追溯到 REQ 编号。
遵循 .claude/shared/sdd-spec-traceability.md，本 Agent 负责的追溯链路：
| 追溯层级 | 标注格式 | 检查方式 |
|---|---|---|
| FS §4.x 功能描述 | **REQ-XXX**：{描述} |
每个 REQ 在 FS 中有对应章节 |
| FS §14 RTM | 全链路追溯矩阵（扩展 BDD/UA/RTL/SVA/UVM/Checker/Coverage 列） | 覆盖率 100% |
| BDD 场景 | **覆盖 REQ**：REQ-XXX + **FS 章节**：§4.x + Checker/Test Case/Coverage |
每个 REQ 至少 1 normal + 1 boundary/error |
追溯图输出（L2/L3 节点）：
FS 文档和 BDD 场景完成后，向 {module}_trace_graph.yaml 追加 L2(FS) 和 L3(BDD) 节点：
# L2: FS 章节节点
- id: FS-{mod}-§4.1
layer: L2
type: fs_section
title: "{功能描述标题}"
ref: "ds/doc/fs/{module}_FS_v1.0.md §4.1"
upstream: [REQ-001]
downstream: [SCN-001, SCN-002]
# L3: BDD 场景节点
- id: SCN-001
layer: L3
type: bdd_scenario
title: "REQ-001_normal_single_transfer"
ref: "ds/doc/fs/{module}_bdd_scenarios.md #SCN-001"
upstream: [REQ-001, FS-{mod}-§4.1]
downstream: [] # 由 verfi-arch/env-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.
- 11d ago First seen · 392 lines · 177 tokens per session scan A 99c224ea7ef4
chip-fs-writer is an agent published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 177 tokens to every session and 6,072 once invoked, about $0.0009 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
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
persona-high
Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
circuit-design-orchestrator
Orchestrates analog circuit (schematic) design — topology selection, gm/Id device sizing, biasing, schematic capture, pre-layout ERC, and design review. Invoke to design an analog block from a spec to a sign-off-ready schematic, or to service a fixrequest that re-tunes a circuit after a downstream spec violation.