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.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/instructions/nozomi-koborinai/terradart/agents-md)<a href="https://agentmods.dev/instructions/nozomi-koborinai/terradart/agents-md"><img src="https://agentmods.dev/badge/instructions/nozomi-koborinai/terradart/agents-md/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/instructions/nozomi-koborinai/terradart/agents-md"><img src="https://agentmods.dev/badge/instructions/nozomi-koborinai/terradart/agents-md.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.13822 | $0.13822 |
| Opus 5.5 | $0.05529 | $0.05529 |
| Sonnet 5.5 | $0.02764 | $0.02764 |
| Haiku 4.5 | $0.01382 | $0.01382 |
Grade A, and why
terradart AGENTS.md 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 today.
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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide
This file is the shared source of truth for coding agents working on TerraDart. Tool-specific files such as .cursor/rules/* should point back here instead of duplicating policy.
Current phase — maintenance + path to beta
The GA hashicorp/google catalog is filled (alpha). The curation push is over; the harness runs in maintenance mode:
| Loop | Cadence | Actor → merge path |
|---|---|---|
| Schema bump, one job + PR per lane: google (+ google-beta ride-along), aws, cloudflare, appwrite, azure | Weekly, staggered: google Sundays, aws Mondays, cloudflare Tuesdays, appwrite Wednesdays, azure Thursdays, 22:00 UTC (schema-bump.yml, crons in tool/providers.yaml bump:) |
the workflow opens the PR and enables auto-merge (squash) when the drift report finds nothing for a human; cloudflare (bump.mode: pr-only) and any other bump wait for the maintainer |
| Wave shipping | On demand, when tool/curation_backlog.yaml has entries |
the maintainer, or a cloud agent asked to follow terradart-ship-wave → an ordinary PR the maintainer merges |
| Ledger paydown | Every release preparation (dart tool/release_ledger_check.dart, run by tool/bump_version.sh) |
the release author pays down or accepts the schema-bump ledgers in the release PR (RELEASE.md) |
Human / maintainer focus in this phase:
- Path to beta — three external-validation gates; the canonical list lives in status (not duplicated here).
- Example-debt paydown — the 2026-08 apply-excluded batch left a large
tool/example_debt.yaml; shrinking it is standing quality work viaterradart-backfill-examples. - Cookbook and docs — real-apply records and user-facing guides.
google-beta support is a filled beta-only catalog (112 resource factories at the current provider pin): packages/terradart_google_beta. Types that also exist in GA stay in terradart_google. There is still no backlog sweep or wave lane for new names — a later provider pin that adds a beta-only type lands on request via terradart-add-beta-resource. Generated against a filtered schema fixture (source_beta/, re-extracted automatically by the weekly schema bump at the GA bump version via extract_schema_subset.dart --resources-from, and by hand only when the curated set changes — never hand-edited; schema.json keys are the single source of truth for the set). Types derive from Magic Modules YAML like GA, with nothing hand-listed: tool/sync_lane_mm_yaml.dart resolves every schema.json resource to its mmv1 file through the header of its generated Go source in hashicorp/terraform-provider-google-beta at the pinned tag (hand-written resources and IAM adjuncts have none) and writes source_beta/mm/ plus the mm_sources.yaml record; wrap_lanes.dart re-syncs on regen whenever that record no longer matches the fixture (so the weekly ride-along refreshes it) and fails the wrap gate on a stale one. The lane wraps with --mm-hints (MM enum_values → enums, MM exactly_one_of → sealed arguments, MM conflicts → nullable sealed arguments), and every beta override sets deriveNestedTypes, deriveOutputGetters, deriveEnums and deriveExactlyOne (yaml_loader_test.dart enforces it; wrap-init --provider hashicorp/google-beta fills them). Universal QA Gate 9 fails the build if a beta-only type appears in the GA schema — promotion means demoting the factory from beta (breaking, maintainer work) while GA curation goes through the backlog. Per-provider pipeline coordinates live in tool/providers.yaml; beta wrappers pin the provider meta-argument (wrap --resource-provider) because beta shares the GA google_* type prefix. Beta inputs that name a GA resource take the terradart_google RefTo type (the ledger's hashicorp/google-beta section inherits the GA rules; referencesFrom: google), so the package depends on terradart_google. Beta examples are synth + terraform validate only. The package releases in lockstep and publishes as publish.yml Phase 4.
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.
- today Changed · +34 tokens per session 28212683fa34
- yesterday Changed · +4 lines · +539 tokens per session 6ae29c9d9ce6
- 14d ago Changed · +96 tokens per session 0142dc1212d9
- 15d ago Changed · +423 tokens per session eea11030f2fb
- 25d ago Changed · +1 lines · +338 tokens per session db2ade54b29a
- 26d ago Changed · +2 lines · +506 tokens per session 93705a609374
- 27d ago Changed · +1 lines · +930 tokens per session 1a719c69afb3
- 28d ago Changed · +40 tokens per session 9c4617ec1dee
- 29d ago Changed · +4 lines · +1,006 tokens per session 38a5dd1f4ba0
- 1mo ago First seen · 281 lines · 9,910 tokens per session scan A d2fe1d10e8c2
terradart AGENTS.md is an instructions file published in the GitHub repository nozomi-koborinai/terradart (52 stars, last pushed today), licensed Apache-2.0. It adds 13,822 tokens to every session, about $0.0553 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.