Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add gear-foundation/vara-skills --skill gtest-tdd-loopgit clone --depth 1 https://github.com/gear-foundation/vara-skillsWrote 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/gear-foundation/vara-skills/gtest-tdd-loop)<a href="https://agentmods.dev/skills/gear-foundation/vara-skills/gtest-tdd-loop"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/gtest-tdd-loop/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/gear-foundation/vara-skills/gtest-tdd-loop"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/gtest-tdd-loop.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.00050 | $0.00311 |
| Opus 5 | $0.00025 | $0.00156 |
| Sonnet 5 | $0.00010 | $0.00062 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
gtest-tdd-loop 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 10d 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.
What it actually says
Gtest Tdd Loop
Overview
Drive local verification through a red-green loop and summarize failures in a machine-readable form.
Start Here
Read ../../references/gtest-cheatsheet.md, ../../references/sails-gtest-and-local-validation.md, and ../../references/gear-gas-reservations-and-waitlist.md.
Use ../../assets/gtest-report-template.md as the output shape.
Write the result to docs/plans/YYYY-MM-DD-<topic>-gtest.md.
Use ../../scripts/run_gtest.sh to execute the loop and ../../scripts/parse_test_output.py to summarize failures.
Workflow
- Write or update the smallest failing gtest case for the current task.
- Verify the test fails for the expected reason.
- Apply the minimal implementation change.
- Run the local loop through
../../scripts/run_gtest.sh. - Capture the parser output and record the final green or remaining gap state.
Guardrails
- Do not skip the failing-test step.
- Do not claim success from compile output alone.
- Keep gtest evidence tied to the current task, not a generic workspace run.
- Escalate if the workspace cannot produce a stable local gtest target.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 36 lines · 50 tokens per session scan A 021e790d8a24
gtest-tdd-loop is a skill published in the GitHub repository gear-foundation/vara-skills (17 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 311 once invoked, about $0.0003 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
nw-fp-fsharp
F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
nw-fp-kotlin
Kotlin language-specific patterns with Arrow, Raise DSL, and coroutine-based effects.
cpp-testing
A guide for testing C++17/20 code with GoogleTest, GoogleMock, CMake, and CTest. It covers unit and integration tests, test discovery, coverage, and sanitizers.
perl-testing
Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.
JavaScript Testing Patterns
Modern JavaScript testing strategies with Jest, Mocha, and testing best practices covering unit testing, integration testing, mocking, async patterns, and DOM testing.