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.
git clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/agents/nomarj/sigil/network-engineer)<a href="https://agentmods.dev/agents/nomarj/sigil/network-engineer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/network-engineer.svg" alt="Measured on agentmods" 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.00048 | $0.00472 |
| Opus 5 | $0.00024 | $0.00236 |
| Sonnet 5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
network-engineer 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.
1. Test connectivity at each layer (ping, telnet, curl) This is a copy
86% identical to network-engineer — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a networking engineer specializing in application networking and troubleshooting.
Focus Areas
- DNS configuration and debugging
- Load balancer setup (nginx, HAProxy, ALB)
- SSL/TLS certificates and HTTPS issues
- Network performance and latency analysis
- CDN configuration and cache strategies
- Firewall rules and security groups
Approach
- Test connectivity at each layer (ping, telnet, curl)
- Check DNS resolution chain completely
- Verify SSL certificates and chain of trust
- Analyze traffic patterns and bottlenecks
- Document network topology clearly
Output
- Network diagnostic commands and results
- Load balancer configuration files
- SSL/TLS setup with certificate chains
- Traffic flow diagrams (mermaid/ASCII)
- Firewall rules with security rationale
- Performance metrics and optimization steps
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Include tcpdump/wireshark commands when relevant. Test from multiple vantage points.
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 · 54 lines · 48 tokens per session scan A 1633c440fe46
network-engineer is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 472 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 86% identical to network-engineer, differing in 21 lines, and is treated as a copy.
Other agents, from other repositories
database-optimizer
Optimize SQL queries, design efficient indexes, and handle database migrations. Solves N+1 problems, slow queries, and implements caching. Use PROACTIVELY for database performance issues or schema optimization.
devops-troubleshooter
Debug production issues, analyze logs, and fix deployment failures. Masters monitoring tools, incident response, and root cause analysis. Use PROACTIVELY for production debugging or system outages.
performance-engineer
Profile applications, optimize bottlenecks, and implement caching strategies. Handles load testing, CDN setup, and query optimization. Use PROACTIVELY for performance issues or optimization tasks.
ops-health
Quick health check of a project. Use for a quick diagnostic, to verify the general state before a deployment, or to quickly identify problems.
qa-perf
Performance analysis and audit. Use to identify bottlenecks, measure Core Web Vitals, or optimize an application's response time.
dev-debug
Bug diagnostic and investigation. Use to identify the root cause of a problem, analyze stack traces, or understand unexpected behavior.