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-agent-verify/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-agent-verify)<a href="https://agentmods.dev/skills/nozomi-koborinai/terradart/terradart-agent-verify"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/terradart/terradart-agent-verify/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-agent-verify"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/terradart/terradart-agent-verify.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.00042 | $0.00731 |
| Opus 5 | $0.00021 | $0.00365 |
| Sonnet 5 | $0.00008 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
terradart-agent-verify 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TerraDart agent verification
Policy and pitfalls live in AGENTS.md at the repo root. This skill is the repeatable done workflow.
Contents
When to use
- Before opening or updating a PR.
- After editing wrapper overrides, generated wrappers, examples, or agent docs.
- After a cloud-agent session claims work is finished.
Workflow
Task progress:
- 1. From the repository root, run
dart pub getif dependencies changed. - 2. Run
tool/agent_verify.shand confirm it exits 0 (agent_verify: OK). This includescheck_example_topology(strict quickstarts only) andapply_smoke_test(cost gate + cost-comment gate test 13). If you added curated factories used in examples, confirmtool/apply_cost_denylist.yamllines includegcp-cost:from MCP (notbilling-behavior:alone unless IAM adjunct). - 3.
example_synth_gates(inside step 2) already synths all quickstarts and runsterraform validateper example whenterraformis onPATH;check_docs_consistencyis the text-only docs check. - 4. If you touched
pubsub_quickstartor synth/export paths, runtool/smoke_quickstart.sh. - 5. Report which commands ran in the PR or task summary.
Optional flags
tool/agent_verify.sh --format # scoped dart format (hand-written packages)
tool/agent_verify.sh --maintainer # add wrap-init / wrap-promote e2e tests
Use --maintainer when changing wrap-init, wrap-promote, or their tests.
Ad-hoc verification pitfalls
- Never trust
cmd | tail -1 && next. A pipeline's exit status is the last command's, sotail/grep/headswallow a failingdart testand the&&chain continues. Run the command bare and check$?directly, or useagent_verify.sh(it setspipefail). - Golden refresh is a copy, not an edit. When
wrapoutput legitimately changes: Level A factory goldens (test/golden/*.factory.expected.dart.golden) take the regenerated wrapper with the 3-line banner stripped (tail -n +4); wrap fixture goldens (test/fixtures/wrap/expected_output/**) take the file verbatim, banner included. Never hand-edit golden contents to make a diff pass.
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 2f8e49e82ffd
- 12d ago First seen · 54 lines · 42 tokens per session scan A e725c002ed1c
terradart-agent-verify is a skill published in the GitHub repository nozomi-koborinai/terradart (46 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 731 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
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
flutter-mcp-toolkit-control
Drive a running Flutter app — tap, scroll, type, fill forms, hot-reload, navigate. Use when you need to interact with the UI.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).
mocktail
Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).
harness-engineering-lifecycle
Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists. Use when refactoring custom validation CLIs/MCPs for large polyrepos, extending Steward across sibling repos, or deploying a local tool to a consumer project for dogfooding and…