What is start-module?

A workflow for building a ViraStack Start module from registry code through its feature page. A module is a reusable feature with screens, data handling, forms, and tests that runs on example data rather than a real API.

Use it to create or change a module, its loading, error, and empty states, its forms and tests, its live preview, and its copyable usage prompt.

It keeps the module consistent across supported project templates and makes clear which parts are provided and which API integration remains the user's job.

start-module — Skill for Claude Code by virastack/start

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 virastack/start --skill start-module

Clone the repo

git clone --depth 1 https://github.com/virastack/start

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/virastack/start/start-module/github.svg)](https://agentmods.dev/skills/virastack/start/start-module)

Your own site

<a href="https://agentmods.dev/skills/virastack/start/start-module"><img src="https://agentmods.dev/badge/skills/virastack/start/start-module/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/virastack/start/start-module"><img src="https://agentmods.dev/badge/skills/virastack/start/start-module.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,711 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.

Model	Per session	Once invoked
Fable 5.1	$0.00103	$0.01711
Opus 5.5	$0.00041	$0.00684
Sonnet 5.5	$0.00021	$0.00342
Haiku 4.5	$0.00010	$0.00171

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

Security

Grade A, and why

start-module 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 2d 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.

.claude/skills/start-module/SKILL.md · 63 lines

How it starts

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

Start module

A module is a working feature the reader copies into their Start project: screens with loading, error and empty states, its data layer, forms and tests. It runs on dummy data with no API. Connecting a real API and adapting the response model is the reader's job; the module only makes that easy. A module never brings a page or route: the reader puts it on a page of their own.

Principles

Own packages first: use @virastack/mask, @virastack/password and @virastack/address where they fit. Check their current docs before writing custom code for the same job.
shadcn stays original: never edit or override files under components/ui. Custom code lives in the module's own components.
Same rules as the templates: feature folder src/features/<name>, no barrels, only the @/* alias, one-way imports, English code and comments.
Every template: the module works in all four (nextjs, tanstack, nextjs-i18n, tanstack-i18n). Only show work in the Next.js template, but change and test all four.

Source (this repository)

registry/<name>/common/src/features/<name>/: shared files.
registry/<name>/<framework>/: framework-specific files that replace or add to common.
registry/<name>/<framework>-i18n/: the i18n layer replaces the common files that hold text and carries messages/tr.json and messages/en.json, which virastack add merges into src/messages.
Register the module in FEATURES in scripts/build-registry.js: name, English title and description, frameworks, route (feature, component, optional fallback and routeSearch), packages for ViraStack packages, minStartVersion.
Dependencies come from the files' imports; template built-ins are left out. registryDependencies is not used.
Tests ship with the module: Vitest, Testing Library and MSW, colocated as *.test.ts(x).

Build and test

npm run check in this repository.
npm run build:registry writes the JSON to ../virastack.com/public/r and runs sync:preview, which copies the module into virastack.com/src/features/start/demos/<name>/ with its install-files.ts. The preview is generated: never edit it by hand.
node scripts/e2e.js --full --only <text> installs a fresh project, runs add <name>, typecheck, lint:ci, test and build with and without the page the site's prompt asks the agent for (scripts/feature-route.ts), then remove <name>. Run it for all four templates before calling the module ready.
remove deletes the module's files, empty folders and messages, and asks before deleting files the reader changed. Check that too.

Read the full file on GitHub · 63 lines

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.

2d ago Changed a274e3d2fbce
3d ago First seen · 63 lines · 103 tokens per session scan A b216ec61bd7c

Subscribe to this mod's changes

start-module is a skill published in the GitHub repository virastack/start (103 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,711 once invoked, about $0.0004 per session on Opus 5.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-11-04.

Frontend TypeScript ai boilerplates cli scaffolding tailwindcss

start-module next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
start-modulevirastack/start	Skill	103	yesterday	MIT	A	103	Claude Code
bun-developmentDokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI	Skill	512	4mo ago	none	A	50	Claude Code, Codex
dd-code-generationDataDog/pup	Skill	1.0k	yesterday	Apache-2.0	A	16	Claude Code
beuistarc007/ui-components	Skill	1.9k	yesterday	MIT	A	81	Claude Code, Codex
beui-prostarc007/ui-components	Skill	1.9k	yesterday	MIT	A	85	Claude Code, Codex
adding-a-commandcaliber-ai-org/ai-setup	Skill	1.3k	1mo ago	MIT	A	76	Claude Code, Codex
scaffold-projectMarve10s/Better-Fullstack	Skill	818	yesterday	MIT	A	80	Claude Code