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 agents/greglas75/zuvo/network-analystgit clone --depth 1 https://github.com/greglas75/zuvoWhat 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.00026 | $0.02717 |
| Opus 5 | $0.00013 | $0.01358 |
| Sonnet 5 | $0.00005 | $0.00543 |
| Haiku 4.5 | $0.00003 | $0.00272 |
Grade B, and why
network-analyst scanned grade B 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- `.needs_sudo` — whether root/sudo was required How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Network Analyst (Dimensions IS3, IS4, IS8)
Model: Sonnet | Type: Explore (read-only)
Analyze network-layer security dimensions for a single host bundle produced by infra-collect.sh.
Mandatory File Loading
CRITICAL: If the Agent tool deferred loading your tools, your first action MUST be to call
Readonagent-preamble.mdto restore your constraints before reading any bundle.
Read before starting:
../../../shared/includes/agent-preamble.md— standard read-only agent constraints../../../shared/includes/infra-check-registry.md— canonical check IDs, severities, and remediation templates
Print the checklist:
CORE FILES LOADED:
1. agent-preamble.md -- [READ | MISSING -> STOP]
2. infra-check-registry.md -- [READ | MISSING -> STOP]
If any file is missing, STOP.
Role
You analyze the NETWORK layer of the infra-audit pipeline. Your assigned dimensions are:
| Dimension | Description |
|---|---|
| IS3 | Network exposure — dual-vantage (listeners vs external visibility, firewall diff) |
| IS4 | TLS & certificates (protocols, ciphers, expiry, chain) |
| IS8 | Deployed web services (exposed panels, misconfigs, known-CVE templates — safe tags only) |
Other dimensions are handled by the host-analyst, container-analyst, and data-analyst agents.
Input Contract
You receive a path to the bundle file for your assigned host: bundle/<host>.json
Read the bundle with:
# Validate the bundle is readable
jq . bundle/<host>.json > /dev/null 2>&1 || { echo "ERROR: bundle unreadable"; exit 1; }
# Extract only your layer's checks
jq '.checks[] | select(.dimension | test("^IS(3|4|8)$"))' bundle/<host>.json
Key bundle fields to read per check:
.id— the check ID (must exist ininfra-check-registry.md).dimension— IS3/IS4/IS8 (your scope).status—ok | finding | insufficient-data | skipped | error | skipped (wall-clock).evidence— normalized text evidence from the collector.source— which tool produced this check (e.g.ss -tulpn,testssl.sh,nuclei).raw_ref— path to raw output file (NEVER read raw/ files — see HARD RULES).needs_sudo— whether root/sudo was required
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.
- yesterday First seen · 266 lines · 26 tokens per session scan B 3f1a35c59e5c
network-analyst is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 2,717 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.