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 Firstp1ck/pi-coding-agent-forge --skill network-diagnosticsgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWrote 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/firstp1ck/pi-coding-agent-forge/network-diagnostics)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/network-diagnostics"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/network-diagnostics/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/firstp1ck/pi-coding-agent-forge/network-diagnostics"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/network-diagnostics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high YARA Match · line 146 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00045 | $0.01897 |
| Opus 5.5 | $0.00018 | $0.00759 |
| Sonnet 5.5 | $0.00009 | $0.00379 |
| Haiku 4.5 | $0.00005 | $0.00190 |
Grade A, and why
network-diagnostics 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 1mo 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.
curl -s -o /dev/null -w "%{http_code}" http://pi.hole/admin/ How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Diagnostics
Diagnose and troubleshoot network issues including connectivity, DNS, ports, and routing.
Quick Start
Connectivity Check
# Check internet connectivity
ping -c 3 1.1.1.1
# Check DNS resolution
dig google.com +short
# Check a local service
curl -s -o /dev/null -w "%{http_code}" http://pi.hole/admin/
DNS Diagnostics
Basic DNS Resolution
# Resolve via system DNS (Pi-hole)
dig example.com +short
# Resolve via specific DNS server
dig @1.1.1.1 example.com +short # Cloudflare
dig @8.8.8.8 example.com +short # Google
dig @pi.hole example.com +short # Pi-hole
# Reverse DNS lookup
dig -x <ip-address> +short
# Full DNS trace
dig example.com +trace
Pi-hole DNS Analysis
# Check if Pi-hole is blocking correctly
# Query a known ad domain — should return 0.0.0.0 or NXDOMAIN
dig @pi.hole ads.google.com +short
# Check Pi-hole query log (recent queries via API)
curl -s "http://pi.hole/admin/api.php?getAllQueries=100" | jq '.data | length'
# Check upstream DNS health
curl -s "http://pi.hole/admin/api.php?getForwardDestinations" | jq '.'
# Check if Pi-hole is enabled
curl -s "http://pi.hole/admin/api.php?status" | jq '.status'
DNS Troubleshooting Flow
DNS not resolving?
├── Can you ping 1.1.1.1?
│ ├── No → Network/routing issue (not DNS)
│ └── Yes → DNS issue confirmed
│ ├── Does dig @1.1.1.1 work?
│ │ ├── No → Upstream DNS blocked (firewall?)
│ │ └── Yes → Local DNS problem
│ │ ├── Does dig @pi.hole work?
│ │ │ ├── No → Pi-hole issue
│ │ │ │ ├── Is pihole-FTL running?
│ │ │ │ ├── Is port 53 listening?
│ │ │ │ └── Check Pi-hole logs
│ │ │ └── Yes → Client DNS config issue
│ │ │ └── Check /etc/resolv.conf
│ │ └── Is /etc/resolv.conf pointing to Pi-hole?
Connectivity Testing
Layer-by-Layer Diagnosis
# Layer 1-2: Physical/Link
ip link show # Interface status
ethtool <interface> # Link speed, duplex
# Layer 3: Network
ip addr show # IP addresses
ip route show # Routing table
ping -c 3 <gateway> # Gateway reachable?
ping -c 3 1.1.1.1 # Internet reachable?
# Layer 4: Transport
ss -tlnp # Listening TCP ports
ss -ulnp # Listening UDP ports
# Layer 7: Application
curl -v http://example.com # HTTP connectivity
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.
- 1mo ago First seen · 252 lines · 45 tokens per session scan A 92001cfd780b
network-diagnostics is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (91 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,897 once invoked, about $0.0002 per session on Opus 5.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
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
confirm-failures-are-causally-linked-to-the-task-before-reportin
When delegating a task affected by this skill, include.
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
ci-fix-monitor
Codex adapter for monitoring and fixing CI failures on opencode-swarm PRs. Use when diagnosing failed checks, fixing package-check (npm tarball) failures, resolving quality/lint/format errors, fixing macOS cross-platform file I/O failures, or watching a PR until all checks are green.
issue-tracer
Use when asked to trace, investigate, root-cause, reproduce, plan, fix, resolve, close, or prepare a PR for an issue, bug report, defect, regression, failing test, or confusing runtime behavior. This Codex adapter delegates to the canonical protocol at .opencode, which owns the Full-Resolution Contract, reproduction…
guardrail-patterns
Codex adapter for opencode-swarm destructive-command guardrail changes. Use before modifying src/hooks/guardrails.ts, checkDestructiveCommand, dcNormalizeCommand, shell-wrapper parsing, .swarm destructive-command blocking, or guardrails unit/adversarial tests.