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 CodeInfinity1/Stram --skill network-and-dns-safetygit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/network-and-dns-safety)<a href="https://agentmods.dev/skills/codeinfinity1/stram/network-and-dns-safety"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/network-and-dns-safety/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/codeinfinity1/stram/network-and-dns-safety"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/network-and-dns-safety.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.00033 | $0.00484 |
| Opus 5.5 | $0.00013 | $0.00194 |
| Sonnet 5.5 | $0.00007 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
network-and-dns-safety 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 1mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network And DNS Safety
Purpose
Network changes can break connectivity or leak data. This skill keeps diagnosis and changes cautious, explicit, and reversible.
When To Use
Use for DNS/ad-block/privacy services, proxy settings, tunnels, firewall rules, network failures, and connectivity-sensitive setup.
Inputs And Evidence
- Desired change, current error, OS/network context, target domain/service, and rollback plan.
- System status and approved diagnostic commands.
Tool Map
dns_lookuphttp_endpoint_checktcp_connectivity_probesystem_statusrun_shell_commandweb-data-extractionlocal-service-monitoringsecrets-handling
Workflow
- Clarify the problem or desired network change.
- Use
dns_lookup,http_endpoint_check, andtcp_connectivity_probefor bounded native diagnostics before shell commands. - Gather non-destructive diagnostics first.
- Identify privacy/security impact.
- Propose a minimal reversible change.
- Apply changes only after approval.
- Verify connectivity and rollback path.
Native Implementation Boundaries
- Use native shell/status tools when approved.
- Do not import external reference AdGuard/DNS plugins.
- Do not modify network settings through hidden scripts.
- Native network tools are diagnostic only; they do not edit DNS, proxy, firewall, tunnel, or adapter settings.
- TCP probing is limited to a single host and port, not scan ranges.
Safety And Approval
- Network changes require explicit user approval.
- Avoid logging sensitive domains/tokens.
- Keep rollback instructions.
Verification
- Before/after diagnostics should be recorded.
- DNS diagnostics should report resolved state, address records, and address classification.
- HTTP diagnostics should report status, redirects, TLS metadata, headers, and errors.
- TCP diagnostics should report reachable state for the single requested host and port.
- Confirm target service behavior.
- Report if admin privileges blocked action.
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.
- 1mo ago First seen · 74 lines · 33 tokens per session scan A b47eae98195a
network-and-dns-safety is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 484 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…