Borrowing it
Nothing to install: this file belongs to nozomi-koborinai/terradart. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nozomi-koborinai/terradart/main/.agents/skills/terradart-tighten-example-topology/SKILL.mdgit clone --depth 1 https://github.com/nozomi-koborinai/terradartWrote 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/nozomi-koborinai/terradart/terradart-tighten-example-topology)<a href="https://agentmods.dev/skills/nozomi-koborinai/terradart/terradart-tighten-example-topology"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/terradart/terradart-tighten-example-topology/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/nozomi-koborinai/terradart/terradart-tighten-example-topology"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/terradart/terradart-tighten-example-topology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.00692 |
| Opus 5.5 | $0.00016 | $0.00277 |
| Sonnet 5.5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
terradart-tighten-example-topology 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 27d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tighten example topology
Use after terradart-backfill-examples when a quickstart gained coverage-only resources that synth + validate but are not linked into the stack.
When to use
- Reviewer or agent notices factories that "exist only to appear in synth output."
dart tool/check_example_topology.dartreports unwired must-reference types on a strict quickstart.- Before merging a large example extension (especially
compute_lb_quickstart).
Workflow
-
1. Identify orphans — resources with no incoming
TfArg.ref/dependsOnfrom siblings. Natural leaf nodes (forwarding rules, IAM members, one-shot jobs, firewalls) do not need incoming refs. -
2. Wire must-reference types (common cases):
Factory type Wire into GoogleComputeSslCertificatesslCertificatesonGoogleComputeTargetSslProxy/GoogleComputeTargetHttpsProxyGoogleComputeRegionSslCertificatesslCertificatesonGoogleComputeRegionTargetHttpsProxyGoogleComputeRegionHealthCheckhealthChecksonGoogleComputeRegionBackendServiceGoogleComputeTargetHttpProxytargetonGoogleComputeGlobalForwardingRule(port 80)GoogleComputeRegionTargetHttpProxytargetonGoogleComputeForwardingRule(regional ILB) -
3. Reorder
add(...)blocks so referenced resources are created before consumers; capturefinal x = add(...)when later siblings needx.*. -
4. Sensitive fields — keep
TfArg.variable+variables.tf.json(see backfill skill). -
5. Register strict quickstarts — add slug to
strict:intool/example_topology_allowlist.yamlwhen the example should enforce must-reference rules in CI. -
6. Verify:
dart tool/check_example_topology.dart dart tool/check_docs_consistency.dart tool/agent_verify.sh
Automation
tool/check_example_topology.dart scans synth JSON for Terraform types listed under must_be_referenced in tool/example_topology_allowlist.yaml. If the resource address appears only once, the quickstart is unwired.
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.
- 27d ago Changed 6d25537c4dc8
- 1mo ago Changed · -2 lines 49dd519b4b4e
- 2mo ago First seen · 53 lines · 41 tokens per session scan A 11ed22ec7745
terradart-tighten-example-topology is a skill published in the GitHub repository nozomi-koborinai/terradart (52 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 692 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-08-30.
Other skills, from other repositories
terraform-infrastructure-as-code
Comprehensive Terraform Infrastructure as Code skill covering resources, modules, state management, workspaces, providers, and advanced patterns for cloud-agnostic infrastructure deployment.
Terraform Infrastructure as Code
Production-grade Terraform development with HCL best practices, module design, state management, multi-cloud patterns, and AI-enhanced infrastructure as code for scalable cloud deployments.
auditing-terraform-infrastructure-for-security
Auditing Terraform infrastructure-as-code for security misconfigurations using Checkov, tfsec, Terrascan, and OPA/Rego policies to detect overly permissive IAM policies, public resource exposure, missing encryption, and insecure defaults before cloud deployment.
terraform-expert
Expert-level Terraform infrastructure as code, modules, state management, and production best practices. Use when the user mentions infrastructure as code, devops, or automation, or when the task involves Terraform Basics, Resource Management, Modules, or State Management.
auditing-terraform-infrastructure-for-security
Auditing Terraform infrastructure-as-code for security misconfigurations using Checkov, tfsec, Terrascan, and OPA/Rego policies to detect overly permissive IAM policies, public resource exposure, missing encryption, and insecure defaults before cloud deployment.
terraform-docs
Terraform 1.15.x — configuration language, resources, variables, modules, state, backends, providers, functions.