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.08676 | $0.08676 |
| Opus 5 | $0.04338 | $0.04338 |
| Sonnet 5 | $0.01735 | $0.01735 |
| Haiku 4.5 | $0.00868 | $0.00868 |
Grade C, and why
terradart AGENTS.md scanned grade C with 2 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
**gcp-cost MCP.** `.cursor/mcp.json` launches [`tool/gcp-cost-mcp-wrapper.sh`](tool/gcp-cost-mcp-wrapper.sh), which materializes the Cursor Secret `GOOGLE_APPLICATION_CREDENTIALS` (inline JSON) to `~/.config/gcp-cost/ser Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
**gcp-cost MCP.** `.cursor/mcp.json` launches [`tool/gcp-cost-mcp-wrapper.sh`](tool/gcp-cost-mcp-wrapper.sh), which materializes the Cursor Secret `GOOGLE_APPLICATION_CREDENTIALS` (inline JSON) to `~/.config/gcp-cost/ser How it starts
The opening of the file, as written. The whole thing — 296 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 CLAUDE.md or .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 (GA + google-beta ride-along) | Sundays 22:00 UTC (schema-bump.yml) |
Monday-morning agent (runbook) → bump-merge.yml executor, gated by BUMP_MERGE_ENABLED |
| Wave shipping | Weekly, Tuesday mornings (Cursor schedule); no-op while tool/curation_backlog.yaml is empty |
agent (runbook) → wave-open.yml + wave-merge.yml executor, gated by WAVE_MERGE_ENABLED |
| Loop health | Mondays 03:00 UTC (loop-health.yml) |
report appended to the loop-health issue |
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 (128 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). 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 examples are synth + terraform validate only (the apply-smoke skip ledger records why). The package releases in lockstep and publishes as publish.yml Phase 4 — its FIRST pub.dev release must be a manual maintainer dart pub publish (OIDC automated publishing only covers packages that already exist there).
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.
- 3d ago Changed · +19 lines · +1,017 tokens per session 0086f882eb85
- 5d ago Changed · +181 tokens per session e789450a341a
- 11d ago First seen · 277 lines · 7,478 tokens per session scan C e6853f9607dc
terradart AGENTS.md is an instructions file published in the GitHub repository nozomi-koborinai/terradart (45 stars, last pushed 2d ago), licensed Apache-2.0. It adds 8,676 tokens to every session, about $0.0434 per session on Opus 5. A static security scan graded it C with 2 findings (asks for root, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).