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 Samurai-goose/SPECTER-The-Illusive-Security-Protocol --skill network-infrastructure-pentestgit clone --depth 1 https://github.com/Samurai-goose/SPECTER-The-Illusive-Security-ProtocolWrote 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/samurai-goose/specter-the-illusive-security-protocol/network-infrastructure-pentest)<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/network-infrastructure-pentest"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/network-infrastructure-pentest/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/samurai-goose/specter-the-illusive-security-protocol/network-infrastructure-pentest"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/network-infrastructure-pentest.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00029 | $0.02221 |
| Opus 5 | $0.00015 | $0.01111 |
| Sonnet 5 | $0.00006 | $0.00444 |
| Haiku 4.5 | $0.00003 | $0.00222 |
Grade A, and why
network-infrastructure-pentest 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Infrastructure Pentest
Purpose
Assess network-layer security: validate segmentation, test firewall rules, enumerate exposed services, analyze routing and switching security, and identify infrastructure-level attack paths. Complements application-layer skills by testing the network foundation that applications depend on.
Triggers
- Network infrastructure authorized for testing
- Recon analysis identifies open ports or exposed services
- User requests network segmentation validation
- Firewall rules or network ACLs available for review
- VPN, remote access, or edge network in scope
Required Inputs
| Input | Description | Required |
|---|---|---|
governance_context |
Active engagement governance record | Yes |
target_ranges |
IP ranges, subnets, VLANs in scope | Yes |
network_diagrams |
Network topology, firewall rule sets (if available) | Recommended |
access_point |
Where testing originates (external, internal, DMZ, VPN) | Yes |
constraints |
Rate limits, no-DoS rules, testing windows | Recommended |
Workflow
-
Scope Verification — Confirm IP ranges, ports, and testing approach are authorized. Note testing windows and rate constraints.
-
Network Discovery & Service Enumeration
- Host discovery (ICMP, TCP SYN, ARP on local segment)
- Port scanning: TCP (SYN, connect), UDP (top 1000+)
- Service version detection and banner grabbing
- OS fingerprinting
- Map: IP → hostname → service → version → state
-
Network Segmentation Validation
Test Method Risk if Failing VLAN isolation Attempt cross-VLAN communication Lateral movement between zones DMZ → Internal Test connectivity from DMZ to internal subnets DMZ compromise reaches internal User → Server Test access from workstation segment to server management Unauthorized server access Guest → Corporate Test guest network access to corporate resources Untrusted device access Dev → Prod Test access from development to production networks Dev compromise reaches production Internet → Internal Test for unfiltered inbound access Direct external attack Internal → Internet Test egress filtering (DNS, HTTP, ICMP, raw IP) Data exfiltration channels
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 · 211 lines · 29 tokens per session scan A 80e18862bf2a
network-infrastructure-pentest is a skill published in the GitHub repository Samurai-goose/SPECTER-The-Illusive-Security-Protocol (2 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 2,221 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…