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 nanxiaoyao/network-huawei-skills --skill interface-configgit clone --depth 1 https://github.com/nanxiaoyao/network-huawei-skillsWrote 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/nanxiaoyao/network-huawei-skills/interface-config)<a href="https://agentmods.dev/skills/nanxiaoyao/network-huawei-skills/interface-config"><img src="https://agentmods.dev/badge/skills/nanxiaoyao/network-huawei-skills/interface-config/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/nanxiaoyao/network-huawei-skills/interface-config"><img src="https://agentmods.dev/badge/skills/nanxiaoyao/network-huawei-skills/interface-config.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.00124 | $0.02831 |
| Opus 5.5 | $0.00050 | $0.01132 |
| Sonnet 5.5 | $0.00025 | $0.00566 |
| Haiku 4.5 | $0.00012 | $0.00283 |
Grade A, and why
interface-config 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 2mo 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
华为交换机接口与链路聚合配置技能 (interface-config)
适用平台 S 系列 V200R011C10+ ｜ CE 系列 V200R022C00+ 文档来源 华为产品文档 dc_cfg_int_* / dc_cfg_eth-trunk_*
接口是所有协议的物理底座 出问题先看接口 Eth-Trunk 链路聚合是接口的逻辑形态 提带宽+冗余
触发场景
- 接口配置 IP / 描述 / 速率 / 双工
- 接口物理 down 不通
- 大量错包 CRC 错 入向丢包
- 配 MTU / 巨帧 jumbo frame
- PoE 供电
- 配置 Eth-Trunk 链路聚合（手工 / LACP）
- LACP 不协商 / 成员口不上线
- 跨设备聚合（M-LAG 堆叠跨设备聚合）
- Trunk 链路两端速率不匹配
物理接口配置
基础属性
interface GigabitEthernet 0/0/1
description To-CoreSW
speed 1000 # 速率 10/100/1000
duplex full # 双工
negotiation disable # 关闭自协商（双方都关或都开 否则速率不匹配）
mtu 9216 # 巨帧（默认 1500）
jumboframe enable 9216
flow-control # 流控
undo shutdown
接口三层化
interface GigabitEthernet 0/0/1
undo portswitch # 转为三层口（仅部分款支持）
ip address 10.1.1.1 24
PoE 供电（S 系列接入交换机）
interface GigabitEthernet 0/0/1
poe enable
poe power max 30000 # 30W 最大功率（mW）
poe priority { critical | high | low }
display poe interface # 查 PoE 状态
display poe power # 查总功耗
错包诊断
display interface GigabitEthernet 0/0/1
# 看 Input/Output errors、CRC、Frames、Drops 等计数
clear counters interface GigabitEthernet 0/0/1
Eth-Trunk 链路聚合
两种模式
| 模式 | 适用 | 协商 |
|---|---|---|
| 手工 manual | 简单 不要协商 | 无 LACP |
| LACP（lacp-static） | 推荐 自动协商 故障检测 | LACP 报文 |
配置 手工模式
interface Eth-Trunk 1
mode manual load-balance # 手工模式 默认就是
quit
interface GigabitEthernet 0/0/1
eth-trunk 1
quit
interface GigabitEthernet 0/0/2
eth-trunk 1
quit
配置 LACP 模式（推荐）
interface Eth-Trunk 1
mode lacp-static
lacp preempt enable
lacp preempt delay 30
max active-linknumber 4
min active-linknumber 1
quit
interface GigabitEthernet 0/0/1
eth-trunk 1
interface GigabitEthernet 0/0/2
eth-trunk 1
LACP 系统优先级与接口优先级
# 系统优先级 决定谁是 Actor 哪边的接口优先级生效
lacp priority 100 # 系统级 默认 32768
# 接口优先级 决定哪些接口为活动接口
interface GigabitEthernet 0/0/1
lacp priority 100 # 接口级
两端比较：系统优先级数值小的胜 然后比较 MAC 接口优先级数值小为活动
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.
- 2mo ago First seen · 300 lines · 124 tokens per session scan A b11548a906c2
interface-config is a skill published in the GitHub repository nanxiaoyao/network-huawei-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 124 tokens to every session and 2,831 once invoked, about $0.0005 per session on Opus 5.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-31.
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…
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
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.
percepxion-oob
Manage Lantronix out-of-band (OOB) infrastructure via Percepxion central management platform: device inventory, serial port inspection via SLC CLI, firmware compliance, config management, security auditing, and closed-loop incident remediation. Use during outages, maintenance windows, compliance cycles, and…