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 agentmods add instructions/bartstc/vite-ts-react-template/code-stylegit clone --depth 1 https://github.com/bartstc/vite-ts-react-templateWhat 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 | $0.00310 | $0.00310 |
| Opus 5 | $0.00155 | $0.00155 |
| Sonnet 5 | $0.00062 | $0.00062 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
vite-ts-react-template code-style.instructions.md 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 yesterday.
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.
What it actually says
Code Style
File Naming
| Category | Convention | Example |
|---|---|---|
| React components | PascalCase | ProductCard.tsx, SignInForm.tsx |
| Storybook stories | PascalCase | ProductCard.stories.tsx |
| Page Objects (E2E) | PascalCase | ProductListPage.ts |
| Everything else | kebab-case | auth-store.ts, use-counter.ts |
Test files mirror source: use-counter.ts → use-counter.test.ts.
File names match the primary export when possible: ProductCard.tsx exports ProductCard component, use-add-product.ts exports useAddProduct hook.
TypeScript
- Use
unknowninstead ofany— refactor or use type guards instead of type assertions (as Type) - Prefer solving problems with TypeScript types over runtime code when possible
- Use named exports exclusively
React
- Split complex
useEffectinto smaller, focused effects - Prefer composition with
childrenprop over prop drilling - Extract business logic to custom hooks or functions — keep components presentational
General
- Prefer immutability and pure functions — return new objects/arrays instead of mutating
- Follow lint/style configs (
.prettierrc,.eslint.config.mjs) — do not reformat to any other style
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.
- yesterday First seen · 35 lines · 310 tokens per session scan A f2ffb008b054
vite-ts-react-template code-style.instructions.md is an instructions file published in the GitHub repository bartstc/vite-ts-react-template (121 stars, last pushed 1mo ago), licensed MIT. It adds 310 tokens to every session, about $0.0015 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 instructions, from other repositories
south-admin-react CLAUDE.md
Instructions for southliu/south-admin-react, covering claude.md, commands, development, code quality and package management.
south-admin-react AGENTS.md
Instructions for southliu/south-admin-react, covering agents.md, 常用命令, 新建页面（重要约定）, 目录结构 and 路由（自动生成）.
CodeReel CLAUDE.md
Instructions for eddiejaoude/CodeReel, covering codereel, core architectural rule (important), diff view (steps mode), key files and 3d effects roadmap.
comet AGENTS.md
Instructions for MetroStar/comet, covering comet, project structure, development guidelines, styling guidelines and unit testing.
eIsland AGENTS.md
AGENTS.md instructions for JNTMTMTM/eIsland, covering codegraph, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
eIsland CLAUDE.md
Claude Code instructions for JNTMTMTM/eIsland, covering codegraph, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.