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-impl-input-triagegit 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-impl-input-triage)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-impl-input-triage"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-impl-input-triage/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-impl-input-triage"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-impl-input-triage.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.00065 | $0.00990 |
| Opus 5 | $0.00032 | $0.00495 |
| Sonnet 5 | $0.00013 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
chip-impl-input-triage 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
输入确认 Skill
任务
激活后第一步：确认所有输入文档的完整性，分类 Must/Should/Could，缺失项暂停等待补充。
必须输入
| ID | 名称 | 优先级 | 缺失行为 |
|---|---|---|---|
| microarch_doc | 微架构文档 | Must | 暂停，列出缺失章节 |
| coding_style | 编码规范 | Must | 使用默认 .claude/rules/coding-style.md |
| cbb_list | CBB 清单 | Should | 进入 RAG 检索补充 |
| protocol_docs | 接口协议文档 | Should | RAG 检索或标注 [待确认] |
| constraints | 关键约束 | Must | 从微架构文档提取 |
执行步骤
- 用
Glob搜索{module}_work/ds/doc/ua/*.md获取微架构文档列表，确认.claude/rules/coding-style.md存在。若文件不存在，暂停并提示用户 - Read 微架构文档，检查 §3~§13 完整性
- 确认编码规范路径（默认
.claude/rules/coding-style.md） - 检查 CBB 清单是否存在，缺失则标注
- 检查接口协议文档，缺失则标注
- 从微架构提取关键约束（频率/复位/DFT）
- 输出输入分类结果
输出
input_status: complete / partial / vaguemissing_items: 缺失项列表
Metrics
执行完成后记录到 {work_dir}/ds/report/metrics/input_triage.json：
{"stage_id": "input_triage", "duration_ms": 0, "iteration_count": 1}
分类规则
- 微架构完整（§3~§13）+ 编码规范 + CBB 清单 → complete
- 微架构存在 + 编码规范，CBB 清单缺失 → partial
- 仅微架构概述，无详细接口/状态机/FIFO → vague（暂停等待补充）
Gate
所有 Must 输入必须存在，否则暂停等待用户补充。
架构冻结
本 Skill 不涉及架构决策，仅检查输入完整性。
使用示例
示例 1：
- 用户：「data_adpt 微架构文档已就绪，帮我检查输入是否完整」
- 行为：读取微架构文档，检查 §3~§13 完整性，确认编码规范路径，检查 CBB 清单和协议文档，输出
input_status: complete/partial/vague
示例 2：
- 用户：「我要开始写 buf_mgr 的 RTL，先做输入确认」
- 行为：检查微架构文档是否存在、端口列表是否完整、FSM/FIFO 章节是否有详细设计，缺失项列出清单并暂停
异常处理
| 场景 | 触发条件 | 处理动作 |
|---|---|---|
| 微架构文档缺失 | 文件路径不存在或为空 | 暂停，提示用户先完成微架构设计 |
| 微架构章节不完整 | §3~§13 有缺失章节 | 列出缺失章节，标注 vague，暂停等待补充 |
| 编码规范路径无效 | 默认 .claude/rules/coding-style.md 不存在 |
提示用户确认编码规范路径 |
| CBB 清单缺失 | 无 CBB 清单文件 | 标注 partial，进入 RAG 检索补充 |
检查点
检查前：
- 确认微架构文档路径有效
- 确认编码规范文件存在
检查后：
- 确认
input_status已输出（complete/partial/vague） - 确认缺失项清单已列出（如有）
- 确认 metrics 已写入
{work_dir}/ds/report/metrics/input_triage.json
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 · 79 lines · 65 tokens per session scan A d242f23ae5ed
chip-impl-input-triage is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 990 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…