Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/zhaixin244-wq/fnwnpx agentmods add skills/zhaixin244-wq/fnw/chip-lint-checkerWrote 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-lint-checker)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-lint-checker"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-lint-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-lint-checker"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-lint-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.00069 | $0.01822 |
| Opus 5 | $0.00034 | $0.00911 |
| Sonnet 5 | $0.00014 | $0.00364 |
| Haiku 4.5 | $0.00007 | $0.00182 |
Grade A, and why
chip-lint-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 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chip Lint Checker
任务
对 RTL 代码执行 Lint 检查。根据配置或自动检测的 EDA 工具，调用对应模板执行。
工具分层
| 层级 | 工具 | 检查范围 | 模板 |
|---|---|---|---|
| L2 综合 | Verilator | 可综合性/位宽/latch/组合环路 | templates/template_a_verilator.sh |
| L3 风格 | Verible | 命名/风格/编码规范 | templates/template_b_verible.sh |
| L2 综合 | Yosys | 组合环路/多驱动/综合可行性 | templates/template_c_yosys.sh |
| L4 专业 | SpyGlass | CDC/Lint/RDC | templates/template_d_spyglass.sh |
| L5 兜底 | LLM Manual | 人工审查 | templates/template_e_manual.md |
目录约定
| 项目 | 路径 |
|---|---|
| Lint 脚本 | {module}_work/ds/run/run_lint.sh |
| 报告目录 | {module}_work/ds/report/lint/ |
| 配置文件 | {module}_work/ds/run/lint_config.json（可选） |
| 模板目录 | .claude/skills/chip-lint-checker/templates/ |
工具路径
| 工具 | 路径 |
|---|---|
| Verilator | tools/oss-cad-suite/bin/verilator |
| Verible | tools/verible/verible-verilog-lint.exe |
| iverilog | tools/oss-cad-suite/bin/iverilog |
| Yosys | tools/oss-cad-suite/bin/yosys |
| SpyGlass | 系统 PATH（需安装） |
执行步骤
Phase 0：工具检测
检查本地工具可用性，确定执行层级：
HAS_VERILATOR=0; HAS_VERIBLE=0; HAS_YOSYS=0; HAS_IV=0
tools/oss-cad-suite/bin/verilator --version >/dev/null 2>&1 && HAS_VERILATOR=1
tools/verible/verible-verilog-lint.exe --version >/dev/null 2>&1 && HAS_VERIBLE=1
tools/oss-cad-suite/bin/yosys --version >/dev/null 2>&1 && HAS_YOSYS=1
tools/oss-cad-suite/bin/iverilog -V >/dev/null 2>&1 && HAS_IV=1
选择逻辑：
| 条件 | 执行模板 |
|---|---|
| 用户指定 SpyGlass | D（跳过检测） |
| Verilator + Verible 可用 | A + B（首选组合） |
| 仅 Verilator 可用 | A |
| 仅 Yosys 可用 | C |
| 均不可用 | E（LLM Manual） |
Phase 1：确定输入
- 从微架构文档或用户指定提取顶层模块名和 RTL 文件列表
- 用
Glob验证 RTL 文件存在，不存在则暂停 - 检查
lint_config.json中blackbox_modules配置（如有）
Phase 2：组装 run_lint.sh
根据选定模板组装脚本。按需加载模板，仅读取需要的模板文件：
run_lint.sh = 文件头 + [模板A] + [模板B] + [模板C] + [模板D] + 汇总
每个模板独立自包含，有自己的变量定义和退出码处理。
Phase 3：执行
mkdir -p {module}_work/ds/report/lint/
cd {module}_work && bash ds/run/run_lint.sh {top} {rtl_files}
What ships with it
5 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.
- 12d ago First seen · 169 lines · 69 tokens per session scan A 1b1be2e968be
chip-lint-checker is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 1,822 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
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…