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-backfill-examples/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-backfill-examples)<a href="https://agentmods.dev/skills/nozomi-koborinai/terradart/terradart-backfill-examples"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/terradart/terradart-backfill-examples/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-backfill-examples"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/terradart/terradart-backfill-examples.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.00038 | $0.01288 |
| Opus 5 | $0.00019 | $0.00644 |
| Sonnet 5 | $0.00008 | $0.00258 |
| Haiku 4.5 | $0.00004 | $0.00129 |
Grade A, and why
terradart-backfill-examples 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 6d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backfill example coverage
Read CONTEXT.md for vocabulary. Wave policy lives in AGENTS.md and terradart-ship-wave. This skill covers pre-existing catalog gaps — factories already curated but not yet in any quickstart synth output.
When to use
- Paying down the apply-excluded legacy: the 2026-08 GA-catalog fill curated
many factories with debt-ledger coverage only, so
tool/example_debt.yamlis now the standing maintenance-phase work queue. - Shrinking
tool/example_debt.yaml(explicit backfill PRs). - After a Wave lands factories in examples, but older debt remains.
- When CI
terraform validatefails on an example you extended.
Workflow
Task progress:
- 1. Pick targets from
tool/example_debt.yaml. Prefer extending the natural quickstart (Storage →storage_quickstart, Compute LB →compute_lb_quickstart) over inventing a new example. - 2. Extend
lib/main.dartwith minimal, self-contained resources that demonstrate real constructor patterns (refs to siblings in the same stack). - 3. Apply pitfall checklist (below) before committing.
- 4. Sensitive / variable fields — use
TfArg.variable('name')in the stack and declare the variable inbin/infra.dartviatf-out/variables.tf.json(see existingcloud_sql_quickstart,firebase_app_check_quickstart,compute_lb_quickstart). - 5. Remove covered lines from
tool/example_debt.yaml. Keep reasoned deferrals only (org/folder scope,iam-adjunct-debt:for binding/policy when sibling member is in synth, etc.). - 6. Tighten topology — wire must-reference factories into siblings; see
terradart-tighten-example-topology. - 7. Verify — from repo root:
dart tool/check_example_topology.dart # unwired SSL cert / health check / HTTP proxy dart tool/example_synth_gates.dart # synth coverage + terraform validate all quickstarts tool/agent_verify.sh - 8. No version bump or catalog count change unless you also curated new factories.
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.
- 6d ago Changed · -2 lines ecb164a420ce
- 12d ago First seen · 73 lines · 38 tokens per session scan A 0b8b58016928
terradart-backfill-examples is a skill published in the GitHub repository nozomi-koborinai/terradart (46 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,288 once invoked, about $0.0002 per session on Opus 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
gcp-expert
Expert-level Google Cloud Platform, services, and cloud architecture. Use when the user mentions Google Cloud, Cloud Functions, BigQuery, or Firestore.
gcloud-cli
Manage Google Cloud projects, IAM, GKE, Cloud Run, and storage with gcloud while checking the active project and deployment target.
oma-tf-infra
Infrastructure-as-code specialist for multi-cloud provisioning using Terraform across any provider (AWS, GCP, Azure, Oracle Cloud). Use for terraform plan/apply, state management, compute, databases, storage, networking, IAM, OIDC, cost optimization, policy-as-code, ISO/IEC 42001 AI controls, ISO 22301 continuity, and…
databricks-platform-provisioning
Provision and test Databricks workspaces. Use when the user asks to create a workspace, set up a new environment, provision infrastructure, bootstrap Databricks, test a workspace, verify a deployment, or run validation checks against a Databricks workspace. Covers Azure, AWS, and GCP.
databricks-deployment-verification
MANDATORY post-deployment verification. After any workspace + Unity Catalog deployment, you MUST run all THREE compute paths against a UC table — classic cluster, serverless SQL warehouse, serverless notebook job. Skipping any of the three is incomplete work. Use whenever a workspace + UC has been freshly deployed or…
databricks-unity-catalog-setup
Set up Unity Catalog on Databricks workspaces. Use when the user asks to configure Unity Catalog, create a metastore, set up catalogs, schemas, external locations, storage credentials, or configure data governance. Covers Azure, AWS, and GCP.