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 agentmods add skills/ai-shell-team/aish/network-path-diagnosenpx skills add AI-Shell-Team/aish --skill network-path-diagnosegit clone --depth 1 https://github.com/AI-Shell-Team/aishWrote 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/ai-shell-team/aish/network-path-diagnose)<a href="https://agentmods.dev/skills/ai-shell-team/aish/network-path-diagnose"><img src="https://agentmods.dev/badge/skills/ai-shell-team/aish/network-path-diagnose.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.01235 |
| Opus 5 | $0.00041 | $0.00617 |
| Sonnet 5 | $0.00016 | $0.00247 |
| Haiku 4.5 | $0.00008 | $0.00123 |
Grade A, and why
network-path-diagnose scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Diagnose network path quality from this host to a target using ping/mtr/curl. How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network path diagnosis
Measure reachability and path quality (packet loss, latency, jitter) from this host to a user-specified target.
Out of scope: cloud VPC/security-group debugging, whole-host lag checks (diagnose_system_lag), DNS-only failures (dns-diagnose), changing routes or firewall rules.
Rules
- Need a target first: ask for IP/host/URL if missing; do not invent defaults.
- Read-only probes: ping/mtr/curl/ss are fine; do not change NICs, routes, or firewall.
- Stop when enough: stop once the symptom is explained; do not add unrelated probes.
- Missing tools: if
mtris absent, fall back toping+traceroute/tracepathand note that in Evidence. - Uncontrollable peers: for public DNS and similar hosts you cannot log into, run forward tests only and state that reverse MTR is impossible.
Workflow
Confirm target & symptom → quick reachability → path quality (mtr) → TCP/port follow-up if needed → answer
1. Confirm inputs
| Input | Notes |
|---|---|
| Target | IP, hostname, host:port, or URL |
| Symptom | unreachable / slow / intermittent loss / bad at certain times |
| Port/protocol | record TCP port if the app uses one (e.g. 443/22) |
2. Quick reachability
getent ahosts <host> | head -5
ping -c 5 -W 2 <host>
curl -sS -o /dev/null -w '%{http_code} time=%{time_total}\n' --connect-timeout 5 <URL>
# or
nc -zv -w 3 <host> <port> 2>&1
- Resolve fails → use or hand off to
dns-diagnose; continue only with a user-provided IP. - ICMP all lost but TCP port works → ICMP likely filtered; switch to TCP path tests; do not call the path “dead”.
3. Path quality (prefer mtr)
command -v mtr
mtr -rwzc 50 <host>
# without mtr:
traceroute -n <host> 2>/dev/null || tracepath -n <host>
ping -c 20 -W 2 <host>
How to read results
| Pattern | Likely meaning |
|---|---|
| High loss on middle hops, last hop and destination OK | Middle boxes may rate-limit ICMP; trust the last hop more |
| Sustained loss or high latency on the last hop | Path or peer/egress problem |
| Latency jumps after a hop | Bottleneck often after that hop |
| Occasional jitter, no sustained loss | Congestion or local Wi-Fi/interference; retest later |
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.
- 5d ago First seen · 148 lines · 82 tokens per session scan A e9712cac4f98
network-path-diagnose is a skill published in the GitHub repository AI-Shell-Team/aish (528 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 1,235 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
completion-script-generator
Generates shell completion scripts for CLI tools. Parses command structure from help output, commander/yargs configs, or manual specification. Produces completions for bash, zsh, and fish that follow each shell's conventions.
taskgo
Maintains a private Git-backed personal project and task control repository using concise current Markdown, derived Git history, ADRs, and status synchronization. Use when tracking tasks, updating project status (STATUS.md), managing ADRs, synchronizing tracker state, delegating tasks to external agents, or generating…
wear-widget
Workflows, checklists, and scripts for reverse-engineering, analyzing, and extracting Wear OS and Android widgets (Glance, AppWidget, ProtoLayout Tiles). Covers manifest declarations, XML configurations, preview asset extraction, and AVD rendering. Use when analyzing APK widget features, extracting widget…
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
jetpack
Looks up AndroidX and Jetpack library facts that change between releases: current artifact versions (ALPHA, BETA, RC, STABLE, SNAPSHOT, build IDs), Maven coordinates for classes/packages, direct dependencies, and published source code. Use when looking up AndroidX/Jetpack library versions, finding Maven coordinates…
emumanager
Manages Android SDKs, system images, emulators, and Android Virtual Devices (AVDs). Provides workflows for bootstrapping the SDK, downloading images, and creating, starting, or stopping AVDs across mobile, Wear OS, TV, and Automotive form factors. Use when setting up Android SDK tools, launching or debugging…