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-frontendgit 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-frontend)<a href="https://agentmods.dev/skills/gear-foundation/vara-skills/sails-frontend"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-frontend/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-frontend"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-frontend.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.00076 | $0.02771 |
| Opus 5 | $0.00038 | $0.01385 |
| Sonnet 5 | $0.00015 | $0.00554 |
| Haiku 4.5 | $0.00008 | $0.00277 |
Grade A, and why
sails-frontend 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 11d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sails Frontend
Goal
Keep frontend work on the typed Sails path first: generated lib.ts plus @gear-js/react-hooks, with @gear-js/api reserved for low-level fallback cases that the Sails stack does not cover cleanly.
Inputs
assets/frontend-bootstrap-checklist.md../../references/sails-frontend-and-gear-js.md../../references/sails-idl-client-pipeline.md../../references/sails-cheatsheet.md../../references/sails-idl-v2-syntax.md— IDL v2 syntax for understanding generated client contracts../../references/sails-gtest-and-local-validation.md../../references/scale-binary-decoding-guide.md../../references/voucher-and-signless-flows.md
Minimal Path (simple apps)
For a straightforward app (counter, single-service CRUD) where the contract is already built:
npx create-vara-app my-dapp --idl path/to/service.idlcd my-dapp && npm install && npm run dev- Verify: one read query renders, one write action shows disabled/pending/success/error states
- Done — the scaffold handles providers, wallet, typed wrappers, and env validation
Skip the rest of this skill unless you need to customize screens, add Next.js support, wire vouchers, or handle advanced flows.
Bootstrap with create-vara-app
When a Sails app needs a frontend — whether the project is brand-new or an existing repo without one — start with create-vara-app.
Prerequisite: the contract must be built first so the .idl file exists. If the .idl is not available yet, build the contract (cargo build) or use create-vara-app without --idl to scaffold with a demo contract.
npx create-vara-app my-dapp --idl path/to/service.idl
npm: https://www.npmjs.com/package/create-vara-app GitHub: https://github.com/gear-foundation/create-vara-app
This scaffolds a Vite + React + TypeScript frontend with:
- Typed query/transaction wrappers from the IDL
- Wallet integration (SubWallet, Polkadot.js, Talisman)
- Live event subscriptions
- Client-side input validation
- Debug panel with runtime IDL explorer
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.
- 11d ago First seen · 234 lines · 76 tokens per session scan A ee8f778ca05e
sails-frontend is a skill published in the GitHub repository gear-foundation/vara-skills (17 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 2,771 once invoked, about $0.0004 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
onchainkit
Build onchain apps with Coinbase's OnchainKit React components - wallets, swaps, NFTs, payments.
adopting-generated-api-types
Use when migrating frontend code from manual API client calls (api.get, api.create, api.surveys.get, api.dashboards.list, new ApiRequest()) and handwritten TypeScript interfaces to generated API functions and types. Triggers on files importing from lib/api, files with api.get . , manual interface definitions that…
dapp-frontend-patterns
Use when building dApp frontends with wagmi v2 and viem. Covers useReadContract, useWriteContract, useSimulateContract, useWaitForTransactionReceipt, wallet connection (RainbowKit), chain switching, and ENS resolution.
scaffold-eth-patterns
Use when building with Scaffold-ETH 2. Covers project structure, custom hooks (useScaffoldReadContract, useScaffoldWriteContract), debug page, deploying contracts, hot reload, and wagmi integration.
crypto-market-dashboard-guide
Guide to building a real-time crypto market dashboard with Next.js, React, and TradingView charts. Features multi-chain portfolio tracking, DeFi position monitoring, price alerts, and social sentiment integration. Production-ready dashboard template.
solana-v1
Solana dApp UI with kit and web3.js. Use when wallet connect, transactions, or Solana address validation in React/Next.js.