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-rtl-bug-checkergit 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-rtl-bug-checker)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-rtl-bug-checker"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-rtl-bug-checker/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-rtl-bug-checker"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-rtl-bug-checker.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.00080 | $0.02767 |
| Opus 5 | $0.00040 | $0.01384 |
| Sonnet 5 | $0.00016 | $0.00553 |
| Haiku 4.5 | $0.00008 | $0.00277 |
Grade A, and why
chip-rtl-bug-checker 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RTL Bug 检查器
基于 data_adpt 实战经验的 RTL Bug 模式检查。chip-code-writer 在每个子模块 RTL 编写完成后调用。
输入
| 参数 | 类型 | 必需 | 说明 |
|---|---|---|---|
| rtl_files | file_path[] | 是 | 待检查的 RTL 文件路径列表 |
| microarch_doc | file_path | 否 | 微架构文档，用于交叉验证 |
输出
| 参数 | 类型 | 说明 |
|---|---|---|
| bug_check_report | object | 每项检查的 PASS/FAIL 结果 + 详情 |
| summary | string | 总结：通过/失败/警告数量 |
检查项（6 大类）
A. 流水线与状态机
| # | 检查项 | 检查方法 | 严重级别 |
|---|---|---|---|
| A1 | FSM 遍历链表时，是否先检查边界再推进指针？ | grep FSM 状态转移，检查边界条件 | Critical |
| A2 | 多周期操作（3+周期）期间，共享状态是否被保护？ | 检查多周期操作中的状态锁存 | Critical |
| A3 | 流水线各级之间是否有正确的数据传递？ | 检查 _r1/_r2 等流水线寄存器传递链 |
Major |
B. 输入锁存
| # | 检查项 | 检查方法 | 严重级别 |
|---|---|---|---|
| B1 | 组合逻辑输出的端口值，是否在时钟沿前锁存？ | 检查组合输出是否在时序逻辑中捕获 | Critical |
| B2 | 跨状态使用的数据，是否在入口处捕获？ | 检查 FSM 入口处的数据锁存 | Major |
| B3 | RAM 请求的地址/长度是否来自锁存的上下文？ | 检查 RAM 操作地址来源 | Major |
C. 接口连接
| # | 检查项 | 检查方法 | 严重级别 |
|---|---|---|---|
| C1 | 新增端口是否在顶层正确连接？ | 对比子模块端口与顶层实例化 | Critical |
| C2 | APB 读回路径是否包含所有状态寄存器？ | 检查 reg_rd_data mux 覆盖范围 | Major |
| C3 | credit_cnt 等状态信号是否可被软件读取？ | 检查状态寄存器的读回路径 | Major |
D. FIFO 与流控
| # | 检查项 | 检查方法 | 严重级别 |
|---|---|---|---|
| D1 | FIFO 读使能是否依赖下游就绪信号？ | 检查 rd_en 的组合逻辑依赖 | Critical |
| D2 | FIFO 深度是否为 2 的幂？ | 检查 DEPTH 参数值 | Major |
| D3 | 满/空判断是否使用多1位指针法？ | 检查 full/empty 判断逻辑 | Major |
E. 位域与宽度
| # | 检查项 | 检查方法 | 严重级别 |
|---|---|---|---|
| E1 | 寄存器位域是否使用 localparam 定义偏移？ | grep 硬编码数字索引 | Major |
| E2 | 赋值两侧位宽是否匹配？ | 检查赋值语句位宽一致性 | Critical |
| E3 | 截位/扩展是否显式标注？ | 检查位宽转换是否有显式操作 | Major |
F. 资源冲突
| # | 检查项 | 检查方法 | 严重级别 |
|---|---|---|---|
| F1 | 同一寄存器数组是否有同周期多写端口？ | 检查数组赋值的 always 块数量 | Critical |
| F2 | alloc/reclaim 冲突时是否有优先级？ | 检查冲突场景的 if-else 优先级 | Critical |
| F3 | 写冲突是否有互斥逻辑？ | 检查同地址写入的互斥条件 | Critical |
执行步骤
读取 RTL 文件 → 第一轮自动化 Grep → 第二轮 LLM 审查 → 汇总结果 → 输出报告
第一轮：自动化 Grep 检查
对每个 RTL 文件执行以下 Grep 命令，结果自动判定 PASS/FAIL：
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 · 226 lines · 80 tokens per session scan A e742c68b19af
chip-rtl-bug-checker is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 2,767 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…