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 automateyournetwork/netclaw --skill kepner-tregoe-network-troubleshootinggit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/kepner-tregoe-network-troubleshooting)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/kepner-tregoe-network-troubleshooting"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/kepner-tregoe-network-troubleshooting/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/automateyournetwork/netclaw/kepner-tregoe-network-troubleshooting"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/kepner-tregoe-network-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 50 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00197 | $0.02516 |
| Opus 5 | $0.00098 | $0.01258 |
| Sonnet 5 | $0.00039 | $0.00503 |
| Haiku 4.5 | $0.00020 | $0.00252 |
Grade A, and why
kepner-tregoe-network-troubleshooting 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kepner-Tregoe for Network Troubleshooting
What this skill is for
This skill gives a network-troubleshooting agent a disciplined method so it reaches a verified root cause before acting, instead of pattern-matching to a familiar cause and swapping components. The entire value is sequencing and separation: appraise before diagnosing, specify before theorizing, verify before fixing, decide before acting, protect before executing.
You will usually have tools that can read network state (telemetry, device configs, routing/ARP/session tables, logs, packet/flow data, inventory/CMDB). Use those tools to gather the evidence that fills the specification — do not reason from memory when you can observe. The method tells you which evidence matters and what to conclude from it.
Non-negotiable principles
- Specify before you hypothesize. Never name a cause until you have drawn the fault's boundary (what IS affected vs. what IS-NOT). The boundary is where the cause hides; skipping it is why troubleshooting drifts from symptom to symptom.
- The IS-NOT carries the answer. Recording what is broken eliminates almost nothing. Recording the nearest comparable thing that could be broken but isn't eliminates whole classes of cause in one line.
- Test every candidate cause against the whole specification. A cause that explains what IS but contradicts an IS-NOT is wrong, however plausible. Prefer the cause that fits with the fewest assumptions.
- Verify in the real world before you fix. A cause proven on paper is a hypothesis until a log line, a counter, a table entry, or a controlled test confirms it. Fixing an unverified cause "fixes" a symptom and leaves the root.
- Separate the incident fix from the permanent fix. Stop the bleeding with the fastest reversible known-good action; the proper fix is a separate, planned decision. Conflating them extends outages.
- Protect every change before executing it. Prevention + contingency with explicit triggers.
- Do not take state-changing actions without authorization. Diagnose and recommend freely. Before any config change, failover, reboot, or traffic-affecting action, confirm with the human/operator unless you have standing authorization for that specific action. Read-only investigation needs no confirmation.
What ships with it
7 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 · 169 lines · 197 tokens per session scan A 8fb9827d6921
kepner-tregoe-network-troubleshooting is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 197 tokens to every session and 2,516 once invoked, about $0.0010 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.