agentmods.dev

sails-feature-workflow

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

A step-by-step workflow for changing behavior in an existing standard Gear or Vara Sails application. It moves from a written feature specification to architecture, task breakdown, implementation, and checks for related messaging or API concerns.

In plain words
What is it for?
Use it to plan and implement features in an existing Sails repository, including specifications, architecture, task lists, API selection, delayed messages, replies, reservations, and waitlists.
Why use it?
It prevents developers from jumping straight into code while leaving unclear requirements, interface decisions, or asynchronous message behavior unresolved.

Skill for Claude Code

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

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

not rated 17repo 1mo ago A scan 55 tokens original MIT

Good fit Use it to plan and implement features in an existing Sails repository, including specifications, architecture, task lists, API selection, delayed messages, replies, reservations, and waitlists.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gear-foundation/vara-skills/sails-feature-workflow
View source ↗ gear-foundation/vara-skills
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-feature-workflow
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-feature-workflow

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gear-foundation/vara-skills/sails-feature-workflow"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-feature-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 808 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.00055 $0.00808
Opus 5 $0.00028 $0.00404
Sonnet 5 $0.00011 $0.00162
Haiku 4.5 $0.00006 $0.00081

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

Security

Grade A, and why

sails-feature-workflow 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.

skills/sails-feature-workflow/SKILL.md · 52 lines

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.

Sails Feature Workflow

Goal

Keep feature work inside an existing Sails repo on an explicit sequence instead of skipping straight to code edits or bypassing the typed client path.

If the request targets a released contract, a new deployed contract version, or V1->V2 evolution, route through ../sails-program-evolution/SKILL.md before normal implementation work continues.

Required Sequence

  1. Clarify the feature in docs/plans/YYYY-MM-DD-<topic>-spec.md with idea-to-spec and ../../assets/spec-template.md.
  2. Plan architecture or public interface in ...-architecture.md with ../sails-architecture/SKILL.md and ../../assets/architecture-template.md.
  3. If the work targets a released contract, introduces a new deployed version, requires cutover planning, or prepares V1->V2 migration, review ../sails-program-evolution/SKILL.md before task breakdown and coding.
  4. If the feature needs API selection across gstd, review ../gear-gstd-api-map/SKILL.md before coding.
  5. If the feature changes async behavior, replies, delays, reservations, or waitlist semantics, review ../gear-message-execution/SKILL.md before coding.
  6. Break the work into tasks in ...-tasks.md with task-decomposer and ../../assets/task-plan-template.md.
  7. If the feature introduces a fungible token, mint/burn roles, token-backed accounting, or native-value exchange, review ../awesome-sails-vft/SKILL.md before coding.
  8. Implement the Rust changes through sails-rust-implementer.
  9. If the public interface changed, refresh the .idl and regenerate the typed client through the repo's standard build.rs path first. For dedicated Rust client crates, prefer the sails-rs build-helper path before a manual generator pipeline.
  10. Run gtest through ../sails-gtest/SKILL.md.
  11. Run smoke validation only after green gtest, using ../sails-local-smoke/SKILL.md.
  • If the feature includes gasless or signless UX, see ../../references/voucher-and-signless-flows.md for the canonical builder recipes, lifecycle, and failure modes. Define the voucher or session flow in the spec and architecture.

Read the full file on GitHub · 52 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. 10d ago First seen · 52 lines · 55 tokens per session scan A ed13d0af121e

Subscribe to this mod's changes

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

Backend and APIsPlanning
Related

Other skills, from other repositories

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

migrate-segw-to-rap

Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…

arc-mcp/arc-1 · 106 tokens

telnyx-messaging-hosted-curl

Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.

team-telnyx/ai · 45 tokens