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 sails-rust-implementergit 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/sails-rust-implementer)<a href="https://agentmods.dev/skills/gear-foundation/vara-skills/sails-rust-implementer"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-rust-implementer/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/sails-rust-implementer"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-rust-implementer.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.00974 |
| Opus 5 | $0.00025 | $0.00487 |
| Sonnet 5 | $0.00010 | $0.00195 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
sails-rust-implementer 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 9d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sails Rust Implementer
Overview
Implement approved tasks in Sails-first Rust workspaces without freelancing new scope. If the task touches a released contract, preserve public routes, reply shapes, emitted events, and generated-client expectations unless the approved architecture explicitly changes them.
Inputs
../../references/sails-cheatsheet.md— core Sails patterns and APIs../../references/sails-rs-imports.md— import paths for sails-rs types../../references/delayed-message-pattern.md— delayed self-message recipe../../references/vara-domain-overview.md— Vara domain context../../references/gear-sails-production-patterns.md— production patterns../../references/gear-messaging-and-replies.md— messaging and reply flows../../references/gear-gas-reservations-and-waitlist.md— gas and waitlist../../references/sails-syscall-mapping.md—Syscall::*API mapping (use instead of rawgcore::*/msg::*/exec::*)
Additional references by task type:
- Token work:
../../references/awesome-sails-token-patterns.md - Released contract changes:
../../references/contract-interface-evolution.md
Consume the approved spec, architecture, and tasks artifacts before changing code.
If the target crate explicitly builds an ethexe path, stop and hand back to a dedicated ethexe workflow instead of extending this standard Sails pack.
Workflow
- Confirm the task is already specified and architecture-approved.
- Identify the smallest code change that satisfies the current task.
- Match the current Sails release conventions before improvising: public service routes use
#[export], events useemit_event, and shared types use#[sails_type](expands toEncode + Decode + TypeInfo + ReflectHashwith correct crate paths). Prefer#[sails_type]over manual derives for all service types, command/query params, and event payloads. Use#[sails_type(crate = my_crate)]when re-exporting from a different crate. - Preserve released routes, reply shapes, emitted events, IDL expectations, and client-facing contract stability unless the task explicitly changes them.
- Keep failure handling aligned with Gear/Vara async semantics.
- Hand local verification to the gtest loop before claiming the task is done.
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.
- 9d ago First seen · 61 lines · 50 tokens per session scan A 9aa35ee19c87
sails-rust-implementer 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 974 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
jolt
Wrap a Rust function in a Jolt zero-knowledge proof.
solana
Use when working on Solana software, including one or more of: Solana client code using TypeScript, Rust libraries that use Solana crates, Anchor programs, Quasar programs, LiteSVM tests, including Rust program files, TypeScript tests, and Anchor.toml or Quasar.toml configuration. Designed to create minimal, reusable…
solana-toolkit-guide
Guide to the Solana Wallet Toolkit — vanity address generation with multi-threaded search, official Solana Labs libraries, Rust and TypeScript implementations. Includes wallet generation, custom address prefixes, and OG names on the blockchain.
solana
Expert guidelines for Solana program development with Rust, Anchor framework, and Web3.js integration.
smart-contracts
Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting)…
solana-development
Build, test, deploy, and audit Solana programs with Anchor or native Rust, and build with ZK Compression (Light Protocol). Use when developing Solana smart contracts, implementing token operations, optimizing compute, deploying to networks, auditing programs for vulnerabilities, or creating compressed tokens/PDAs.