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 te-path-analysisgit 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/te-path-analysis)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/te-path-analysis"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/te-path-analysis/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/te-path-analysis"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/te-path-analysis.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 Data Exfiltration · line 14 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00060 | $0.01739 |
| Opus 5 | $0.00030 | $0.00870 |
| Sonnet 5 | $0.00012 | $0.00348 |
| Haiku 4.5 | $0.00006 | $0.00174 |
Grade A, and why
te-path-analysis 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 7d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ThousandEyes Path Analysis & Troubleshooting
MCP Servers
- Community:
src/server.py(stdio, Python 3.12+) —te_get_path_visfor path visualization - Official:
https://api.thousandeyes.com/mcp(remote HTTP) — full path vis, BGP, instant tests, anomalies, endpoint agents
Key Capabilities
Path Visualization
| Source | Tool | What It Does |
|---|---|---|
| Community | te_get_path_vis |
Hop-by-hop path from a specific agent to the test target |
| Official | Get Path Visualization | Network paths with routing details |
| Official | Get Full Path Visualization | Comprehensive path data aggregated across all agents |
Path visualization shows every network hop between agent and target:
- IP address and DNS name of each hop
- Latency per hop (pinpoints where delay is introduced)
- Packet loss per hop (identifies lossy links)
- MPLS labels (reveals traffic engineering paths)
- Network owner (ISP/carrier identification per hop)
BGP Route Analysis
| Tool | What It Does |
|---|---|
| Get BGP Test Results | BGP reachability — which BGP monitors see the prefix, which don't |
| Get BGP Route Details | AS path, origin AS, prefix length, route stability |
BGP analysis provides external routing visibility:
- Prefix reachability from ThousandEyes' global BGP monitor fleet
- AS path — is traffic routing through expected carriers?
- Route changes — detect BGP hijacks, leaks, or suboptimal routing
- Origin validation — verify the prefix originates from the correct AS
Outage Investigation
| Tool | What It Does |
|---|---|
| Search Outages | Find network and application outages with time/scope filters |
| List Events | Network/application problems with affected targets |
| Get Event Details | Deep dive: impacted tests, affected agents, timeline |
Active Troubleshooting
| Tool | What It Does |
|---|---|
| Instant Tests | Run tests on demand from selected agents — don't wait for scheduled cycles |
| Get Anomalies | Detect metric deviations from baseline over time |
| Views Explanations | AI-powered explanation of test results and visualizations |
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.
- 7d ago First seen · 142 lines · 60 tokens per session scan A 366ba61759bb
te-path-analysis is a skill published in the GitHub repository automateyournetwork/netclaw (655 stars, last pushed 4d ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,739 once invoked, about $0.0003 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
seedance-troubleshoot
This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause diagnosis.
Debugging Strategies
Advanced debugging patterns for test failures covering root cause analysis, flakiness investigation, performance debugging, and systematic troubleshooting methodologies.
huawei-cloud-mrs-host-fault-diagnose
Huawei Cloud MRS cluster fault diagnosis skill. Diagnoses service faults, instance faults, and host faults through progressive root cause localization: quick log scan first, host troubleshooting when host issues are found, detailed investigation when no conclusion is reached. Driven by the built-in LakeWatch API…
huawei-cloud-mrs-host-alarm-diagnose
Huawei Cloud MRS cluster alarm diagnosis skill. Analyzes the root cause of an MRS alarm based on user-provided alarm information (alarm ID, alarm name, alarm details, occurrence time, node IP, related service and logs), then outputs the root cause, repair steps, and verification method. Diagnosis is driven by the…
huawei-cloud-cdn-abnormal-status-code-analysis
Diagnose CDN business abnormal HTTP status codes (4xx/5xx) using hcloud CLI. Discover and quantify 4xx/5xx volume, localize the exact status code and time window, fork edge-generated vs origin-generated via back-to-source status statistics, correlate top-N distribution, narrow root cause on CDN edge config or origin…
epistemic-graph-troubleshooting
Diagnose and recover a live epistemic-graph engine (the AI-native database): engine down / socket refused, host-daemon crash-loop, circuit-breaker open, backend-type errors, zombie containers, duplicate Swarm tasks, slow first boot. Use when the KG is unreachable, ingestion stalls, go tools error, or a deploy left the…