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-chkgit 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-chk)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-spyglass-cdc-chk"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-spyglass-cdc-chk/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-chk"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-spyglass-cdc-chk.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.00073 | $0.02301 |
| Opus 5 | $0.00036 | $0.01151 |
| Sonnet 5 | $0.00015 | $0.00460 |
| Haiku 4.5 | $0.00007 | $0.00230 |
Grade A, and why
chip-spyglass-cdc-chk 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chip SpyGlass CDC Checker
使用 SpyGlass 工具对 RTL 执行 CDC（Clock Domain Crossing）检查。
When to Use
- 多时钟域设计的 RTL 完成后
- 需要验证跨时钟域信号是否正确同步
- CDC 签核（sign-off）前的检查
- 子模块交付前的 CDC 验证
工具路径
| 工具 | 路径 |
|---|---|
| SpyGlass | 系统 PATH（需安装 Synopsys SpyGlass） |
目录约定
| 项目 | 路径 |
|---|---|
| CDC 脚本 | {module}_work/ds/run/run_cdc.sh |
| SGDC 约束 | {module}_work/ds/run/{module}.sgdc |
| 报告目录 | {module}_work/ds/report/cdc/ |
| Waiver 文件 | {module}_work/ds/run/{module}.cdc.waiver |
| 模板目录 | .claude/skills/chip-spyglass-cdc-chk/templates/ |
核心工作流
Phase 0: 输入确认
├─ 确认顶层模块名和 RTL 文件列表
├─ 确认时钟域信息（来自 FS/微架构文档）
└─ 确认 Black Box 模块列表
Phase 1: 生成 SGDC 约束
├─ 基于时钟域信息生成 clock/reset 定义
├─ 生成 abstract_port（Black Box 端口）
├─ 生成 set_case_analysis（MUX 选择端）
└─ 生成 quasi_static（配置寄存器）
Phase 2: 执行 CDC Setup
├─ 运行 cdc_setup Goal
├─ 检查 autoclocks.sgdc / autoresets.sgdc
├─ 人工审查推导结果，删除非时钟/复位信号
└─ 合并到主 SGDC 文件
Phase 3: 执行 CDC Setup Check
├─ 运行 cdc_setup_check Goal
├─ 修复所有 Error
└─ 确保所有 Flip-Flop 有时钟
Phase 4: 执行 Clock/Reset Integrity
├─ 运行 clock_reset_integrity Goal
└─ 修复 Glitch/Race 问题
Phase 5: 执行 CDC Verify
├─ 运行 cdc_verify_struct（结构检查）
├─ 运行 cdc_verify（功能检查）
└─ 按优先级分类违例
Phase 6: 报告汇总
├─ 生成 cdc_summary.log
└─ 输出违例分类统计
Phase 0：输入确认
-
从微架构文档或用户指定提取：
- 顶层模块名
- RTL 文件列表
- 时钟域信息（时钟名、频率、来源）
- 复位信息（复位名、极性、同步/异步）
- Black Box 模块列表（PLL、第三方 IP 等）
-
用
Glob验证 RTL 文件存在 -
检查是否已有 SGDC 文件，有则复用
Phase 1：生成 SGDC 约束
根据输入信息生成 {module}.sgdc，参考模板 templates/template_cdc_setup.sh。
SGDC 必须包含
# 1. 顶层模块
current_design {module}
# 2. 时钟定义（从 FS/微架构获取）
clock -name "clk_main" -period 10 -edge 0 5
clock -name "clk_bus" -period 20 -edge 0 10
# 3. 复位定义
reset -name "rst_n" -value 0
# 4. Black Box 端口约束（如有 Black Box）
abstract_port -module pll_top -ports clk_out -clock clk_main
# 5. MUX 选择端约束（时钟 MUX）
set_case_analysis -value 0 [get_ports test_mode]
# 6. 准静态信号（配置寄存器）
quasi_static -name "cfg_*"
SGDC 编写规则
What ships with it
3 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 · 229 lines · 73 tokens per session scan A 435b85dc2e08
chip-spyglass-cdc-chk is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 2,301 once invoked, about $0.0004 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…