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/khazp/vibe-coding-prompt-template/testsgit clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-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.00116 | $0.00116 |
| Opus 5 | $0.00058 | $0.00058 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
vibe-coding-prompt-template tests.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 3d 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
Testing Instructions
Read agent_docs/testing.md.
- Add the test level required by the Tech Design.
- Do not delete, weaken, or skip unrelated tests to make a pipeline pass.
- For UI work, include browser/device verification where required.
- For AI features, include direct, indirect, negative, auth-required, failure, and trajectory checks.
- Report exact commands and results in the PR or final handoff.
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.
- 3d ago First seen · 14 lines · 116 tokens per session scan A cea6cc2fb3ee
vibe-coding-prompt-template tests.instructions.md is an instructions file published in the GitHub repository KhazP/vibe-coding-prompt-template (3,027 stars, last pushed 12d ago), licensed MIT. It adds 116 tokens to every session, about $0.0006 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
vibe-code-kit CLAUDE.md
Claude Code instructions for 910jmiguel/vibe-code-kit, covering project: [fill in your project name], tech stack, project structure, key commands and install dependencies.
cherry-studio AGENTS.md
AGENTS.md instructions for CherryHQ/cherry-studio, a project described as: AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs.
NeoHaskell CLAUDE.md
Instructions for neohaskell/NeoHaskell, a project described as: ⏩ NeoHaskell is a dialect of Haskell that is focused on newcomer-friendliness and productivity.
tree-sitter-analyzer CLAUDE.md
Instructions for aimasteracc/tree-sitter-analyzer, covering ruflo — claude code configuration, rules, test quality rules — locked (2026-06-28), t-1: no new test files for existing plugins (blocker) and t-2: no weak assertions — ratchet-enforced (blocker).
nezha AGENTS.md
AGENTS.md instructions for hanshuaikang/nezha, covering nezha — agents.md, 项目概述, 开发命令, 架构设计 and 前端（src/）.
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.