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-ship-wave/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-ship-wave)<a href="https://agentmods.dev/skills/nozomi-koborinai/terradart/terradart-ship-wave"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/terradart/terradart-ship-wave/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-ship-wave"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/terradart/terradart-ship-wave.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.00046 | $0.02626 |
| Opus 5 | $0.00023 | $0.01313 |
| Sonnet 5 | $0.00009 | $0.00525 |
| Haiku 4.5 | $0.00005 | $0.00263 |
Grade A, and why
terradart-ship-wave 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship a TerraDart Wave
Read CONTEXT.md for vocabulary. Generation policy is in AGENTS.md. For each new google_* factory, follow terradart-add-curated-resource first; this skill covers the release boundary around a Wave.
The GA catalog is filled: Waves now originate from new resources the
weekly schema bump appends to tool/curation_backlog.yaml, and catalog counts
move as increments on the completed baseline.
PR scope
Ship one Wave per PR when possible. Do not bundle:
- unrelated example
pubspec.yaml/ workspace version-debt sweeps - release version bumps for a different Wave
- agent-guide-only edits with factory work
If example debt must land with a Wave, limit changes to the quickstart that exercises the new factories. See PR granularity in AGENTS.md.
Wave complete definition
A Wave PR is not done when wrappers and curatedDoc land alone. It is done when:
- Curated factories — overrides linted,
terradart wrapregenerated, API diff reviewed. - Runnable example — new
examples/<name>_quickstartor extend an existing example so every new/breaking factory appears in synth output. Machine-checked bydart tool/example_synth_gates.dart(synthtfTypecoverage, API-enablement deps,terraform validateon every quickstart); a factory may instead get a reasonedtool/example_debt.yamlentry, but that is an explicit reviewed decision. For pre-existing debt backfill, seeterradart-backfill-examples. IAM binding/policy preference: for new*IamBinding/*IamPolicywhen the sibling*IamMemberis already curated and already in synth, prefertool/example_debt.yamlwith reason tokeniam-adjunct-debt:over extending examples solely for coverage. The synth gate enforces the token. If the quickstart provisions a high-cost resource (seetool/apply_cost_denylist.yaml), it must be inapply_smoke_skip.yaml(existence-billed: licenses/reservations) orapply_smoke_pr_skip.yaml(hourly-billed) — the cost gate intool/apply_smoke_test.shfails the build otherwise. Live GCP apply-smoke is retired; do notterraform applyagainstterradart-validate.- New resource types are cost-classified in
tool/apply_cost_denylist.yaml(safe/sweep_only/never_apply); unclassified types fail apply-smoke test9 (default-deny). Confirm cost on two axes — price via the gcp-cost MCP (SKU lookup) and billing behavior via terraform MCP + docs (existence-billed vs hourly) — then classify, recording the basis in the ledger comment. License/SPLA-style services absent from the Cloud Billing Catalog fall back to docs/pattern. When unsure, leave unclassified (the example stays skipped).
- New resource types are cost-classified in
- Breaking changes —
MIGRATING.mdentry and example updated to the new API. - Counts & docs —
tool/doc_expectations.dart,catalog_count_test.dart,wrap_command_test.dart, README / package catalog count phrases (do not rebuild a per-factory dump in## What ships— detail lives on Coverage), agent/website catalog phrases, examplepubspec.yamlcarets. - CI matrix — nothing to wire: the
terraform_validatematrix derives fromexamples/automatically (tool/select_changed_examples.dart). - Verify —
terradart-agent-verify(tool/agent_verify.sh).
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 2da844f0d45a
- 12d ago First seen · 142 lines · 46 tokens per session scan A 7cf38d982714
terradart-ship-wave is a skill published in the GitHub repository nozomi-koborinai/terradart (46 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 tokens to every session and 2,626 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
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
oma-scm
SCM (software configuration management) and Git: branching, merges, conflicts, worktrees, baselines, audit readiness, plus Conventional Commits and safe staging.
oma-dev-workflow
Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination.
release-plugin
Prepare and execute a new release for the flutter-intellij plugin, including updating dependencies, compatibility bounds, changelogs, and verification.
publish-notes
Draft user-facing release notes, store changelogs, and internal publish summaries.
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".