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-interface-contractorgit 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-interface-contractor)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/chip-interface-contractor"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-interface-contractor/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-interface-contractor"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/chip-interface-contractor.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.00058 | $0.00728 |
| Opus 5 | $0.00029 | $0.00364 |
| Sonnet 5 | $0.00012 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
chip-interface-contractor 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 11d 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.
What it actually says
Chip Interface Contractor
任务
输出工业级精确的模块接口契约文档。
执行步骤
- 确认接口类型（AXI4/ACE/CHI/TileLink/自定义握手/APB/AHB 等）。
- 生成端口列表表格： | 信号名 | 方向 | 位宽 | 时钟域 | 复位值 | 描述 |
- 定义时序参数表格： | 参数名 | 最小值 | 典型值 | 最大值 | 单位 | 条件 |
- 描述事务级行为（VALID/READY 握手规则、突发传输顺序、原子操作支持）。
- 生成关键协议的 SystemVerilog Assertion 模板（如握手不丢数据、无组合环路、复位后稳定等）。
- 标注 CDC 相关信号（若为跨时钟域接口）及同步策略。
输出格式
- 端口列表（Markdown 表格）
- 时序参数表
- 事务行为描述（条目式）
- SVA 断言代码块（```systemverilog）
- 接口约束与风险提示
使用示例
示例 1：
- 用户：「为 data_adpt 的上游 AXI4 接口定义接口契约」
- 行为：确认 AXI4 协议和 Slave 角色，生成端口列表表格（信号名/方向/位宽/时钟域/复位值），定义时序参数（setup/hold），生成 SVA 断言模板
示例 2：
- 用户：「帮我定义 buf_mgr 与 ctrl_fsm 之间的自定义握手接口」
- 行为：按 Valid-Ready 协议生成端口列表，定义握手时序参数，生成握手稳定性 SVA（
valid && !ready |=> valid），标注 CDC 信号
异常处理
| 场景 | 触发条件 | 处理动作 |
|---|---|---|
| 协议版本未指定 | 用户未明确 AXI4/ACE/CHI 版本 | 默认使用最新版本，标注 [PROTO-ASSUMED] |
| 接口类型未知 | 非标准协议且无参考文档 | 按自定义握手协议处理，标注 [PROTO-CUSTOM] |
| CDC 信号未标注 | 跨时钟域接口缺少同步策略 | 标注 [CDC-TODO]，提示用户补充同步方案 |
检查点
检查前：
- 确认接口类型（AXI4/APB/自定义等）已明确
- 确认模块角色（Master/Slave）已确定
检查后：
- 确认端口列表包含所有信号且位宽正确
- 确认时序参数表已生成
- 确认 SVA 断言覆盖握手稳定性和数据稳定性
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.
- 11d ago First seen · 56 lines · 58 tokens per session scan A 120357170d94
chip-interface-contractor is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 728 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-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.