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 skills add zhaixin244-wq/fnw --skill chip-traceability-linkergit 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/skills/zhaixin244-wq/fnw/chip-traceability-linker)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-traceability-linker"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-traceability-linker/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/skills/zhaixin244-wq/fnw/chip-traceability-linker"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-traceability-linker.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.00068 | $0.00753 |
| Opus 5 | $0.00034 | $0.00377 |
| Sonnet 5 | $0.00014 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
chip-traceability-linker 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 9d 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
Chip Traceability Linker
任务
建立并输出需求追溯矩阵（Requirements Traceability Matrix, RTM）。
执行步骤
- 用
Glob搜索{module}_work/ds/doc/fs/*.md获取 FS 文档列表，用Glob搜索{module}_work/ds/doc/ua/*.md获取 UA 文档列表。若文件不存在，暂停并提示用户 - 收集需求 ID（如 SysReq-001）及其描述。
- 为每条需求映射到：
- 架构决策 ID（Arch-XXX）
- 接口/信号（Intf-XXX）
- PPA 指标（PPA-XXX）
- 验证策略（Verify-XXX）
- 状态（Allocated / Designed / Verified / Waived）
- 识别未被覆盖的需求或没有上游需求的孤儿架构项。
- 若涉及版本变更，标注新增/删除/修改的追溯链。
输出格式
Markdown 表格： | 需求 ID | 需求描述 | 架构决策 | 接口/信号 | PPA 指标 | 验证策略 | 状态 | 备注 |
随后输出：
- 覆盖率统计（X/Y = Z%）
- 遗漏项清单（如有）
使用示例
示例 1：从 FS 和 UA 构建 RTM
用户：帮我为 data_adpt 模块建立需求追溯矩阵，FS 在 ds/doc/fs/data_adpt_FS_v1.0.md，UA 在 ds/doc/ua/
预期行为：
- 读取 FS 中所有 REQ-XXX 需求
- 扫描 UA 文档，匹配每条需求的架构决策、接口信号、PPA 指标
- 输出完整 RTM 表格 + 覆盖率统计
示例 2：检查遗漏项
用户：检查 data_adpt 的 RTM 有没有未覆盖的需求
预期行为：扫描 RTM，列出所有状态为"未分配"或"待设计"的需求项
异常处理
| 场景 | 触发条件 | 处理动作 |
|---|---|---|
| 需求 ID 缺失 | FS 中无 REQ 编号 | 暂停，提示用户先补充需求编号 |
| 架构文档不完整 | UA 缺少对应章节 | 标注"待设计"，继续追溯其他项 |
| 覆盖率过低 | < 70% | 高亮警告，列出所有未覆盖需求 |
| 版本变更 | 新旧版本差异大 | 逐项标注新增/删除/修改，用户确认后更新 RTM |
检查点
- 追溯前：展示需求 ID 列表和可用架构文档，确认追溯范围
- 追溯后：展示覆盖率统计和遗漏项，用户确认后输出最终 RTM
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.
- 9d ago First seen · 61 lines · 68 tokens per session scan A e9ad2ff680b1
chip-traceability-linker is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 753 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.