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 salatmaster/keenetic-mcp --skill keenetic-troubleshootgit clone --depth 1 https://github.com/salatmaster/keenetic-mcpWrote 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/salatmaster/keenetic-mcp/keenetic-troubleshoot)<a href="https://agentmods.dev/skills/salatmaster/keenetic-mcp/keenetic-troubleshoot"><img src="https://agentmods.dev/badge/skills/salatmaster/keenetic-mcp/keenetic-troubleshoot/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/salatmaster/keenetic-mcp/keenetic-troubleshoot"><img src="https://agentmods.dev/badge/skills/salatmaster/keenetic-mcp/keenetic-troubleshoot.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.00048 | $0.00995 |
| Opus 5 | $0.00024 | $0.00498 |
| Sonnet 5 | $0.00010 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
keenetic-troubleshoot 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- keenetic-troubleshoot — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working out what is wrong with the network
Start from the symptom and work outward. Each step below either finds the fault or rules out a whole class of them, so do not skip ahead.
"The internet is down"
1. Is it the internet or the router?
get_internet_status
The flags separate the cases:
internet: false,gatewayAccessible: false- the link to the provider is down. Go to step 2.gatewayAccessible: true,dnsAccessible: false- the connection is up and DNS is the problem. Go to step 3.captiveAccessible: falseon a hotel or public uplink - a captive portal is intercepting traffic.- everything true - the router is fine and the problem is on one device. Go to the device section.
2. The uplink itself
list_interfaces { "kind": "wan" }
link: "down" means no signal on the physical port: cable, provider, or modem.
link: "up" with state: "down" means the interface is administratively
disabled, which someone or something turned off.
Check which link actually carries traffic:
list_routes { "kind": "default" }
If the default route points at a VPN tunnel rather than the physical WAN, and that tunnel is down, the internet is unreachable even though the provider is fine. That is a common cause and easy to miss.
3. DNS
rci_call { "method": "GET", "path": "show/dns-proxy" }
Then confirm the tunnel or upstream the DNS traffic depends on is actually up
with list_interfaces { "kind": "vpn" }.
"One device cannot get online"
get_device { "mac": "..." }
Read in this order:
blocked: true- access is denied for it. That is the answer.scheduleset - it may be outside its allowed hours.policyset - it leaves through a specific link. Check that link is up withlist_interfaces { "kind": "vpn" }.active: false- the router has not seen it recently. This is a connectivity problem between the device and the router, not a policy problem.
"Wi-Fi is bad"
get_wifi_status
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 · 135 lines · 48 tokens per session scan A 9749e884cf3d
keenetic-troubleshoot is a skill published in the GitHub repository salatmaster/keenetic-mcp (22 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 995 once invoked, about $0.0002 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
keenetic-troubleshoot
Use when someone reports the internet is down, Wi-Fi is bad, a device cannot connect, or the network is slow on a Keenetic router - an ordered playbook that narrows the fault instead of guessing.
keenetic-segments
Use when creating an isolated network on a Keenetic - a guest network, an IoT network, a segment routed through a VPN - explains why the obvious way produces a working network the web interface refuses to list, and the VLAN it is actually missing.
keenetic-rci
Use when a Keenetic question is not covered by the curated tools and you need rcicall - explains the RCI tree, the paths that exist, the responses that will blow up your context, and the traps that make a wrong call look like success.
keenetic-safe-changes
Use before changing anything on a Keenetic router - explains that changes are not saved until asked, what the router's fail-safe does and does not protect against, and the order that avoids locking yourself out.
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…