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 ripmilla/netwalk --skill netwalk-diaggit clone --depth 1 https://github.com/ripmilla/netwalkWrote 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/ripmilla/netwalk/netwalk-diag)<a href="https://agentmods.dev/skills/ripmilla/netwalk/netwalk-diag"><img src="https://agentmods.dev/badge/skills/ripmilla/netwalk/netwalk-diag/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/ripmilla/netwalk/netwalk-diag"><img src="https://agentmods.dev/badge/skills/ripmilla/netwalk/netwalk-diag.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 Rogue Agent · line 82 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00110 | $0.02485 |
| Opus 5 | $0.00055 | $0.01242 |
| Sonnet 5 | $0.00022 | $0.00497 |
| Haiku 4.5 | $0.00011 | $0.00248 |
Grade A, and why
netwalk-diag 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
netwalk-diag
Part of the netwalk read-only network survey toolkit. Toolkit lives at {{TOOLKIT}}.
netwalk-scan answers what is out there. This skill answers what is wrong with it.
Read-only, and it is enforced
Config is exported, never imported or edited. Not one command changes device state — that
includes clear counters, dmesg -C, systemctl restart and debug, all of which the gate
refuses. If a device needs a change, that is a finding with a recommendation, and the site owner
decides. Run everything through netwalk_exec.py so the guarantee holds and the command lands in
the evidence log.
1. Collect
Assumes a credential exists (netwalk-login) and the vendor is known.
T={{TOOLKIT}}
python3 $T/scripts/netwalk_exec.py run --site acme-hq --host gw01 \
--cmd-file $T/scripts/packs/mikrotik.config.txt \
--out ~/.netwalk/sites/acme-hq/configs/gw01.conf \
--evidence ~/.netwalk/sites/acme-hq/evidence.jsonl
python3 $T/scripts/netwalk_exec.py run --site acme-hq --host gw01 \
--cmd-file $T/scripts/packs/mikrotik.health.txt \
--evidence ~/.netwalk/sites/acme-hq/evidence.jsonl
Packs: mikrotik, cisco, aruba, hp, fortinet, linux, windows, each with a
.config.txt, a .health.txt and a .security.txt. Record the exported config path in
config_export_path — relative to the site folder, never pasted into the report.
Run the security pack too, and run it with --out — it deliberately pulls the parts of the
configuration that hold community strings and key material, so its output must land on disk
rather than in the conversation:
python3 $T/scripts/netwalk_exec.py run --site acme-hq --host gw01 \
--cmd-file $T/scripts/packs/mikrotik.security.txt \
--out ~/.netwalk/sites/acme-hq/configs/gw01.security.txt \
--evidence ~/.netwalk/sites/acme-hq/evidence.jsonl
Always use --out for a config export. With --out the full text is written straight to a
0600 file and only a one-line summary is printed. Without it, the whole config comes back through
you — and a vendor config is packed with PSKs, SNMP communities, RADIUS secrets, password hashes and
container environment variables. Anything that reaches you is transmitted to a model API and written
into the session transcript, and neither can be un-sent.
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 · 177 lines · 110 tokens per session scan A 7849b4269e77
netwalk-diag is a skill published in the GitHub repository ripmilla/netwalk (78 stars, last pushed 18d ago), licensed MIT. It adds 110 tokens to every session and 2,485 once invoked, about $0.0006 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
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.