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/firstp1ck/pi-coding-agent-forge/network-diagnosticsnpx skills add Firstp1ck/pi-coding-agent-forge --skill network-diagnosticsgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWhat 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.00045 | $0.01897 |
| Opus 5 | $0.00023 | $0.00949 |
| Sonnet 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 3d 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.
- 3d 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 (74 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 1,897 once invoked, about $0.0002 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.