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-doc-structurergit 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-doc-structurer)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-doc-structurer"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-doc-structurer/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-doc-structurer"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-doc-structurer.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.00057 | $0.00751 |
| Opus 5 | $0.00028 | $0.00376 |
| Sonnet 5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
chip-doc-structurer 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 12d 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 Doc Structurer
任务
为芯片模块微架构规格书设计完整的文档架构与章节权重。
执行步骤
- 询问模块名称、版本号（如 v1.0）、目标工艺节点（可选）。
- 基于 IEEE/工业实践，生成以下标准章节结构：
-
- 文档控制（版本、作者、评审记录）
-
- 引言（目的、范围、定义与缩略语、参考文档）
-
- 模块概述（定位、应用场景、关键特性）
-
- 接口定义（端口列表、协议、时序）
-
- 微架构设计（数据通路、控制逻辑、状态机）
-
- PPA 规格与预算（延迟、吞吐、功耗、面积）
-
- 风险与缓解（时序、功耗、验证、CDC、低功耗、可靠性）
-
- RTL 实现指导（编码规范、Clock/Reset、可综合性）
-
- 附录（RTM、变更记录、参考文献）
-
- 为每个章节分配内容权重（以百分比表示），并标注必须包含的图表/表格数量建议。
- 如果用户提到要从历史版本或相似项目继承模板，说明差异点并给出迁移建议。
输出格式
以 Markdown 表格输出： | 章节 | 权重 | 必填图表/表格 | 备注 | 随后输出完整大纲（带三级标题）。
使用示例
示例 1：设计微架构文档结构
用户：帮我设计 data_adpt 模块的微架构文档结构
预期行为：生成 9 章标准结构 + 权重分配 + 必填图表清单
示例 2：从旧版本迁移
用户：基于 v1.0 的文档结构，帮我升级到 v2.0，新增了低功耗设计
预期行为：对比 v1.0 结构，标注新增章节（低功耗），给出迁移建议
异常处理
| 场景 | 触发条件 | 处理动作 |
|---|---|---|
| 模块信息缺失 | 未提供模块名 | 暂停，提示用户提供模块名称和版本号 |
| 工艺节点未知 | 未指定工艺 | 使用通用结构，PPA 章节标注"待工艺确认" |
| 继承模板不可用 | 旧版本文件不存在 | 从标准模板生成，标注"无历史参考" |
| 章节权重不闭合 | 总和 ≠ 100% | 自动归一化，提示用户确认 |
检查点
- 设计前：展示模块名称、版本、工艺信息，确认输入正确
- 设计后：展示章节权重表和大纲，用户确认后输出完整文档结构
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.
- 12d ago First seen · 58 lines · 57 tokens per session scan A 64ce8622490a
chip-doc-structurer is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 751 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…