sails-gtest

sails-gtest is a skill for Claude Code from gear-foundation/vara-skills. It costs 49 tokens per session (828 once invoked), scanned A, original, MIT.

A testing workflow for Sails programs using Gear/Vara’s gtest framework, generated clients, and explicit test evidence before live-node checks.

In plain words
What is it for?
Use it to prepare and run Sails feature tests, decode replies, reason about gas, and record results in a dated plan document.
Why use it?
It provides a repeatable way to verify features, investigate failures, and add regression coverage before testing against a live network. gtest is a local test environment for checking program behavior.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the vara-skills plugin — 26 skills shipped together

Good fit Use it to prepare and run Sails feature tests, decode replies, reason about gas, and record results in a dated plan document.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gear-foundation/vara-skills/sails-gtest
Install

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.

Any agent
npx skills add gear-foundation/vara-skills --skill sails-gtest
Clone the repo
git clone --depth 1 https://github.com/gear-foundation/vara-skills

Made for: Claude Code.

Or install vara-skills, the plugin that ships this one along with the rest of its 26 skills.

Wrote 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.

agentmods badge for sails-gtest

README.md
[![agentmods](https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-gtest/github.svg)](https://agentmods.dev/skills/gear-foundation/vara-skills/sails-gtest)
Your own site
<a href="https://agentmods.dev/skills/gear-foundation/vara-skills/sails-gtest"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-gtest/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.

agentmods 80×15 button for sails-gtest

Your own site · 80×15
<a href="https://agentmods.dev/skills/gear-foundation/vara-skills/sails-gtest"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-gtest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 828 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.00828
Opus 5 $0.00024 $0.00414
Sonnet 5 $0.00010 $0.00166
Haiku 4.5 $0.00005 $0.00083

Measured 12d ago against content hash 1494ca5d472c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

sails-gtest 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 12d 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.

skills/sails-gtest/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sails Gtest

Goal

Run the Sails-first test loop with generated clients and explicit gtest evidence before any live-node smoke step.

Inputs

  • ../../assets/gtest-report-template.md — report format for gtest results
  • ../../references/gtest-cheatsheet.md — quick reference for gtest APIs
  • ../../references/gtest-patterns.md — common test patterns
  • ../../references/sails-cheatsheet.md — Sails patterns and APIs
  • ../../references/sails-gtest-and-local-validation.md — full gtest and validation guide
  • ../../references/gear-gas-reservations-and-waitlist.md — gas reasoning for tests
  • ../../references/scale-binary-decoding-guide.md — decoding raw reply bytes
  • ../../references/sails-syscall-mapping.mdSyscall::* API for gas, message, and execution context

Write the result to docs/plans/YYYY-MM-DD-<topic>-gtest.md.

Expected Loop

  1. Confirm the implementation target is ready for verification.
  2. Use generated clients or GtestEnv instead of hand-built payloads where the workspace supports them.
  3. If the test must go below generated clients, first decide whether the payload or reply bytes are Sails-routed, plain SCALE, or metadata-driven state output; then apply the raw mental model: send_bytes* returns a MessageId, run_next_block returns the BlockRunResult, and the reply evidence lives in the block result.
  4. Pick the right BlockRunMode and advance blocks explicitly when replies or deferred effects depend on progression.
  5. Use run_to_block when delayed work or timeout behavior spans multiple blocks.
  6. Assert behavior, replies, events, or accounting in the test result, not just compilation.
  7. Record failure mode, fix, and passing command output in the gtest note.
  8. Route to ../sails-local-smoke/SKILL.md only after the suite is green.

Common Pitfalls

  • Rust 2024 listener lifetime: Under edition 2024 capture rules, chaining generated-client calls into listen() can fail with "temporary value dropped while borrowed". In Sails 1.0 the service client implements Listener directly, so bind the service client before listening:
    let client = program.service_name();
    let mut events = client.listen().await.unwrap();
    

Read the full file on GitHub · 61 lines

Files

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.

Changes

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.

  1. 12d ago First seen · 61 lines · 49 tokens per session scan A 1494ca5d472c

Subscribe to this mod's changes

sails-gtest is a skill published in the GitHub repository gear-foundation/vara-skills (17 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 828 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.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens