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-rdc-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-rdc-resolver)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-spyglass-rdc-resolver"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-spyglass-rdc-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-rdc-resolver"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-spyglass-rdc-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.00075 | $0.01971 |
| Opus 5 | $0.00037 | $0.00986 |
| Sonnet 5 | $0.00015 | $0.00394 |
| Haiku 4.5 | $0.00007 | $0.00197 |
Grade A, and why
chip-spyglass-rdc-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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chip SpyGlass RDC Resolver
分析 SpyGlass RDC 报告,通过 LLM 与知识库中的 RDC 规则信息,对 RTL 进行分析,给出修改建议或生成 waiver 文件。
When to Use
- 处理
chip-spyglass-rdc-chk生成的 RDC 报告(rdc_summary.log、rdc_verify.log) - 需要分析 RDC 违例的根因并给出 RTL 修改建议
- 需要为可接受的违例生成 waiver 文件
- RDC 签核前的违例清理
核心工作流
0. 加载 Blackbox 模块列表
1. 解析 RDC 报告 → 提取 (rule, severity, file, line, message) 元组
2. 过滤 Blackbox → 模块在 blackbox 列表中的违例自动 waive
3. 按优先级分类违例 → P0~P4
4. 对 P0/P2 违例:必须修复,LLM 分析 RTL 给出修改方案
5. 对 P1/P3/P4 违例:LLM 分析判断是否真问题,修复或 waive
6. 输出:RTL 修改建议 + waiver 文件
Step 0: 加载 Blackbox 模块列表
读取 blackbox-modules.md(本 SKILL.md 同目录),加载 blackbox 模块列表。
判定规则:
- 模块名匹配 blackbox 列表条目,或
- 违例文件路径包含 blackbox 模块名
如果 blackbox-modules.md 为空或不存在,跳过此步骤。
Step 1: 解析 RDC 报告
RDC 报告来自 chip-spyglass-rdc-chk 的输出,典型路径:
{module}_work/ds/report/rdc/rdc_summary.log— 汇总报告{module}_work/ds/report/rdc/3_rdc_verify.log— 亚稳态检查{module}_work/ds/report/rdc/4_rdc_verify_corrupt.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 列表中。Blackbox waive 的违例在 waiver 文件中单独一节输出。
Step 3: 按优先级分类违例
查 rdc-rules-reference.md(本 SKILL.md 同目录)中的规则映射表。
如果规则不在映射表中,标记为 "unknown rule" 并提示用户手动分类。
Step 4: 执行优先级动作
| 优先级 | 动作 | 输出 |
|---|---|---|
| P0 (Async Reset Metastability) | 必须修复。 添加复位同步器或设置 reset ordering | RTL 修改建议 |
| P1 (Reset-less Path Corruption) | 分析判断。 添加 qualifier 或 safe-stating 逻辑 | 修复或 waive |
| P2 (RDC on Clock Path) | 必须修复。 复位信号禁止组合逻辑驱动时钟 | RTL 修改建议 |
| P3 (Reset Convergence) | 分析判断。 检查复位是否正确分组 | 修复或 waive |
| P4 (Power Domain RDC) | 分析判断。 需 UPF 确认隔离/开关 | 修复或 waive |
关键规则:P0 和 P2 绝对禁止 waive,必须从设计层面修复。
Step 5: 生成输出
5a. RTL 修改建议 (rdc_fix_proposal.md)
# RDC Fix Proposal
## Summary
- Total violations: N
- Blackbox waived: N
- P0 must-fix: N (Async Reset Metastability)
- P2 must-fix: N (RDC on Clock Path)
- P1/P3/P4 reviewed: N
- Fix required: N
- Waived: N
- Unknown rules: N
## P0 — Must Fix (NEVER Waive)
### [P0] Ar_asyncreset01 — <file>:<line>
**Violation:** <message>
**Root Cause:** <分析>
**Fix:**
```verilog
// Before
<原始代码>
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 · 202 lines · 75 tokens per session scan A 1568b6023401
chip-spyglass-rdc-resolver is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 1,971 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…