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 tonone-ai/tonone --skill forge-networkgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/forge-network)<a href="https://agentmods.dev/skills/tonone-ai/tonone/forge-network"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/forge-network/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/tonone-ai/tonone/forge-network"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/forge-network.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.00059 | $0.00827 |
| Opus 5.5 | $0.00024 | $0.00331 |
| Sonnet 5.5 | $0.00012 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
forge-network 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 17d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design and Build Networking
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Detect Environment
Scan the project to determine the target platform and existing networking config:
# Check for Terraform networking resources
grep -rl 'google_compute_network\|aws_vpc\|azurerm_virtual_network\|cloudflare_zone' *.tf **/*.tf 2>/dev/null
# Check for existing IaC
ls *.tf terraform/ modules/ Pulumi.yaml cdk.json 2>/dev/null
# Check for cloud CLI configs
gcloud config get-value project 2>/dev/null
aws sts get-caller-identity 2>/dev/null
cat wrangler.toml 2>/dev/null
cat fly.toml 2>/dev/null
# Check for existing network-related configs
ls nginx.conf Caddyfile docker-compose.yml 2>/dev/null
If no platform is detected, ask. Match the IaC tool already in use (Terraform, Pulumi, etc.).
Step 1: Understand the Topology
Determine:
- How many services need to communicate?
- Which services are public-facing vs internal-only?
- Single region or multi-region?
- Any compliance requirements (data residency, PCI, HIPAA)?
- Expected traffic patterns (steady, bursty, regional)?
Use what's already in conversation context. Only ask what you don't know.
Step 2: Generate Network Architecture
Generate IaC for the full networking stack:
VPC / Subnet Layout:
- Separate public and private subnets
- Dedicated subnets per tier (web, app, data)
- CIDR blocks sized for growth but not wastefully large
- Secondary ranges for pods/services if Kubernetes is involved
Firewall / Security Groups:
- Default deny all inbound
- Allow only required ports between tiers
- No 0.0.0.0/0 ingress except to the load balancer on 443
- Egress restricted where possible
- Each rule documented with its purpose in a comment
Load Balancer:
- HTTPS termination with managed certificates
- HTTP-to-HTTPS redirect
- Health check endpoints configured
- Connection draining enabled
- WAF / Cloud Armor / Shield if the workload warrants it
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.
- 17d ago First seen · 107 lines · 59 tokens per session scan A c2052e909355
forge-network is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 59 tokens to every session and 827 once invoked, about $0.0002 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-27.
Other skills, from other repositories
id-sync
The infra-delivery POST-MERGE GitOps reconcile-and-observe driver (step 13) — the PROCEDURE the generic agent runs AFTER merge (merge IS the deploy trigger) to drive the GitOps controller's idempotent reconcile toward the GATE-MERGED IaC, PINNED to the merged candidatesha (argocd app sync/refresh, reusing the shipped…
id-architect
The read-only forward-design ENTRY mode (infra-delivery step 2) — for "the app runs locally, there is NO deployment yet — design where it should run." Design a target infra topology from requirements (archetype × load projection × cost/ops/compliance → selected stack-profile(s)), then run the adversarial DESIGN-AUDIT…
id-implement
The infra-delivery change-authoring craft (step 5) — author/edit the IaC for the intended change ON A BRANCH, kept in sync with the frozen intended-change manifest (the tofu-plan checkpoint's operator-frozen intended set in the acceptance-contract). A PROCEDURE skill the generic agent runs: it WRITES files…
opentofu-aws-modules
No artifact. This skill emits prescriptive guidance inline. The implementing agent writes the OpenTofu/Terraform files in the assigned IaC worktree.
data-tier-cutover
The stateful-tier migration PROCEDURE skill — cut an app's SQL database + cache over from self-managed instances to a managed serverless target. A read-only procedure the generic agent runs alongside the id- infra-delivery steps: it drives the fail-closed cutover-mechanism DECISION TREE (snapshot-restore vs…
id-import
The read-only live-env → IaC import entry mode (infra-delivery step 2) — survey an existing AWS/Kubernetes environment that has NO IaC, codify it into OpenTofu/Kubernetes IaC, and prove fidelity by the acceptance seam tofu plan == ∅ (the IaC equals reality). A PROCEDURE skill the generic agent runs: the aws/tofu reads…