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-spyglass-cdc-resolvergit 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-spyglass-cdc-resolver)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-spyglass-cdc-resolver"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-spyglass-cdc-resolver/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-spyglass-cdc-resolver"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-spyglass-cdc-resolver.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.02274 |
| Opus 5 | $0.00034 | $0.01137 |
| Sonnet 5 | $0.00014 | $0.00455 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
chip-spyglass-cdc-resolver 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.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chip SpyGlass CDC Resolver
分析 SpyGlass CDC 报告，通过 LLM 与知识库中的 CDC 规则信息，对 RTL 进行分析，给出修改建议或生成 waiver 文件。
When to Use
- 处理
chip-spyglass-cdc-chk生成的 CDC 报告（cdc_summary.log、cdc_verify.log） - 需要分析 CDC 违例的根因并给出 RTL 修改建议
- 需要为可接受的违例生成 waiver 文件
- CDC 签核前的违例清理
核心工作流
0. 加载 Blackbox 模块列表
1. 解析 CDC 报告 → 提取 (rule, severity, file, line, message) 元组
2. 过滤 Blackbox → 模块在 blackbox 列表中的违例自动 waive
3. 按优先级分类违例 → P0~P7
4. 对 P0 违例：必须修复，LLM 分析 RTL 给出修改方案
5. 对 P1~P7 违例：LLM 分析判断是否真问题，修复或 waive
6. 输出：RTL 修改建议 + waiver 文件
Step 0: 加载 Blackbox 模块列表
读取 blackbox-modules.md（本 SKILL.md 同目录），加载 blackbox 模块列表。
判定规则：
- 模块名匹配 blackbox 列表条目，或
- 违例文件路径包含 blackbox 模块名（如
ip/pll_top/pll_clk_gen.v匹配pll_top）
Blackbox 模块典型类型：
- 第三方 IP（非团队所有）
- 已验证 IP（已 tape-out 证明）
- 硬宏或模拟封装
- 明确排除在 CDC 检查范围外的模块
如果 blackbox-modules.md 为空或不存在，跳过此步骤。
Step 1: 解析 CDC 报告
CDC 报告来自 chip-spyglass-cdc-chk 的输出，典型路径：
{module}_work/ds/report/cdc/cdc_summary.log— 汇总报告{module}_work/ds/report/cdc/5_cdc_verify.log— 详细违例{module}_work/ds/report/cdc/4_cdc_verify_struct.log— 结构检查
SpyGlass 日志格式：
Warning [<rule_name>] <file>:<line> <message>
Error [<rule_name>] <file>:<line> <message>
提取：rule_name、severity、file path、line number、violation message。
如果日志格式未知，要求用户粘贴样本或指定格式。
Step 2: 过滤 Blackbox 违例
对每个解析出的违例，检查其模块是否在 blackbox 列表中：
module_name ← 从文件路径提取（如 "pll_top" 从 "ip/pll_top/pll_clk_gen.v"）
if module_name in blackbox_list:
→ 标记为 BLACKBOX_WAIVED，跳过优先级分析
所有 blackbox waive 的违例在 waiver 文件中单独一节输出。
Step 3: 按优先级分类违例
查 cdc-rules-reference.md（本 SKILL.md 同目录）中的规则映射表。
rule_name → P0/P1/P2/P3/P4/P5/P6/P7
如果规则不在映射表中：
- 标记为 "unknown rule"
- 提示用户手动分类
Step 4: 执行优先级动作
| 优先级 | 动作 | 输出 |
|---|---|---|
| P0 (Ac_unsync01/02) | 必须修复，禁止 waive。 LLM 分析 RTL，给出同步器添加方案 | RTL 修改建议 |
| P1 (Ac_conv01~05) | 分析判断。 LLM 检查是否真收敛问题。若是 → 用 gray_signals 或异步 FIFO 修复；若否 → waive | 修复或 waive |
| P2 (Ac_glitch*) | 分析判断。 LLM 检查同步器输入是否来自寄存器。若否 → 修复；若是 → waive | 修复或 waive |
| P3 (Ac_cdc01) | 分析判断。 LLM 检查快→慢时钟域信号是否需要脉冲展宽 | 修复或 waive |
| P4 (Ac_datahold01a) | 分析判断。 LLM 检查 qualifier 保护下数据是否稳定 | 修复或 waive |
| P5 (Ac_cdc08) | 分析判断。 LLM 检查多 bit 信号是否需要异步 FIFO | 修复或 waive |
| P6 (Ar_*) | 分析判断。 LLM 检查异步复位是否需要同步释放 | 修复或 waive |
| P7 (Ac_fifo01) | 分析判断。 LLM 确认异步 FIFO 正确性 | 修复或 waive |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 224 lines · 68 tokens per session scan A 02c660713075
chip-spyglass-cdc-resolver 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 2,274 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
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface…