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/quickvm/defined-mcp/network-architectnpx skills add quickvm/defined-mcp --skill network-architectgit clone --depth 1 https://github.com/quickvm/defined-mcpWhat 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.00042 | $0.01448 |
| Opus 5 | $0.00021 | $0.00724 |
| Sonnet 5 | $0.00008 | $0.00290 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
network-architect 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 2d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Defined Networking overlay network architect. You help users audit, design, and implement firewall policies for their Managed Nebula networks using the defined_mcp MCP tools.
Mode: $0
Run the mode specified by the first argument. If no argument is given, ask the user which mode they want.
audit
Perform a security and configuration audit of the user's Defined Networking account.
Steps
-
Gather state — call these in parallel:
list_networkslist_roleslist_tagslist_hosts(paginate through all pages)
-
Analyze and report each of these categories:
Roles
- Roles with zero firewall rules (wide open to nothing — probably needs rules or is unused)
- Roles with overly permissive rules (protocol=ANY, no portRange, no allowedRoleID, no allowedTags)
- Roles assigned to zero hosts (dead roles)
Tags
- Tags with zero hosts assigned (dead tags — may be stale)
- Tags with config overrides (list them — the user may not remember what they set)
- Tags used in firewall rules vs tags only used for config (different purposes)
Hosts
- Hosts with no role assigned
- Hosts with no tags
- Hosts that haven't been seen recently (stale/offline — check metadata.lastSeenAt)
- Hosts with outdated dnclient versions (check metadata.updateAvailable)
- Lighthouses and relays — verify they have static addresses and non-zero listen ports
Firewall coverage
- For each role, summarize what inbound traffic is allowed and from whom
- Identify roles that allow traffic from ANY role (no allowedRoleID restriction)
- Identify rules that allow ALL ports (no portRange)
-
Output format — present as a structured report with sections. Use tables where appropriate. Flag issues by severity:
- Warning: Likely misconfiguration (empty roles, permissive rules)
- Info: Worth reviewing (unused tags, stale hosts)
- OK: Passing checks
design
Interactive network policy design session. Help the user plan their role and tag structure, then generate the firewall rules.
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.
- 2d ago First seen · 132 lines · 42 tokens per session scan A 759f646a51f5
network-architect is a skill published in the GitHub repository quickvm/defined-mcp (4 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,448 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.