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/workflowgit 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.00194 | $0.00194 |
| Opus 5 | $0.00097 | $0.00097 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
vite-ts-react-template workflow.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 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.
What it actually says
Workflow
Scanning Repository
- Analyze using only files mentioned in the prompt or directly relevant to the task
- Check for
AIDEV-*anchors in relevant subdirectories before scanning broadly
Anchor Comments
Use AIDEV-NOTE:, AIDEV-TODO:, or AIDEV-QUESTION: for inline knowledge (≤ 120 chars, greppable).
- Grep for existing anchors before scanning files
- Update anchors when modifying associated code
- When an anchor is stale, update it instead of removing it; flag if unsure
- Add anchors when code is complex, critical, confusing, or potentially buggy
Implementation
- Run
pnpm lint --fixafter making changes - Stay within current task context — inform dev if a fresh start is needed
- When a task is done, verify it works before reporting completion
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 First seen · 26 lines · 194 tokens per session scan A 851175f64a78
vite-ts-react-template workflow.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 194 tokens to every session, about $0.0010 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.