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 bartstc/vite-ts-react-template --skill writing-specgit clone --depth 1 https://github.com/bartstc/vite-ts-react-templateWrote 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/bartstc/vite-ts-react-template/writing-spec)<a href="https://agentmods.dev/skills/bartstc/vite-ts-react-template/writing-spec"><img src="https://agentmods.dev/badge/skills/bartstc/vite-ts-react-template/writing-spec/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/bartstc/vite-ts-react-template/writing-spec"><img src="https://agentmods.dev/badge/skills/bartstc/vite-ts-react-template/writing-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 38 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 178 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 51 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00069 | $0.03045 |
| Opus 5.5 | $0.00028 | $0.01218 |
| Sonnet 5.5 | $0.00014 | $0.00609 |
| Haiku 4.5 | $0.00007 | $0.00304 |
Grade A, and why
writing-spec 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 1mo 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Guide the developer through writing a feature spec before any code is written. The spec constrains intent and approach so implementation decisions are explicit, reviewed, and traceable. This skill produces three files in specs/NNN-feature-name/ — requirements.md, design.md, tasks.md — using the templates in ./templates/.
Prerequisites
- Read
./templates/requirements-template.md,./templates/design-template.md,./templates/tasks-template.md, and./templates/contract-template.mdbefore starting — they define the section structure - Read
@docs/architecture.mdto understand current building block types and project structure - Determine the next available sequence number by checking both
specs/directory listings ANDgit logfor prior spec-related commits — use the higher of the two
Workflow: Four Phases with Gates
Each phase ends with a human review gate. Do NOT advance to the next phase without explicit developer approval ("continue", "ok", "next", "looks good", or similar). If something goes wrong, STOP and re-plan — do not push forward.
Phase 1 — Goal & Scope (Intent)
Collaborate with the developer to fill requirements.md.
- Ask the developer to describe the feature in 2-5 sentences (or accept what they've already provided)
- Before drafting, ask 3-5 clarifying questions about scope boundaries, error scenarios, and unstated assumptions — only where the answer would change the spec. Skip obvious ones.
- If the feature introduces new API calls (queries or mutations): explicitly ask which server-side error responses each call must handle, and how the UI should react to each.
- Draft the Goal & Context section — focus on the problem, not the solution
- Draft Requirements using EARS notation:
WHEN [condition] THE SYSTEM SHALL [behavior]. Assign stable IDs (R1, R2, …) - Draft Non-Goals — ask: "What should this feature explicitly NOT do?"
- Present
requirements.mdfor review
What to ask if unclear: "What's the observable user behavior when this works correctly?" Never invent requirements — if the developer hasn't specified a behavior, ask about it.
What ships with it
4 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.
- 1mo ago First seen · 181 lines · 69 tokens per session scan A eaf963944e0f
writing-spec is a skill published in the GitHub repository bartstc/vite-ts-react-template (123 stars, last pushed 14d ago), licensed MIT. It adds 69 tokens to every session and 3,045 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
weapp-vite-react-best-practices
A Chinese-language guide for building React 19 WeChat mini programs with weapp-vite and @weapp-vite/react. WeChat mini programs are small apps that run inside WeChat.
typescript-react
Apply, review, and explain React conventions from the TypeScript Style Guide. Use automatically for TypeScript and TSX tasks involving prop-derived state, prop typing, component responsibilities, data flow, compound components, or client and server state.
git
A guide to common Git version-control workflows. Git records changes to code so developers can work in branches, combine changes, and review project history.
github
A guide to using GitHub CLI, a command-line tool for working with GitHub repositories. It covers issues, pull requests, releases, labels, milestones, and workflow runs.
storybook
A guide for writing Storybook stories, which are isolated examples used to develop and document interface components. It focuses on the current Component Story Format and reusable component inputs.
github-actions
A guide for creating and maintaining GitHub Actions workflows, which are automated jobs that run in a repository, such as tests or deployments. It also covers action versions and common security risks.