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/andreaskarz/vibe-coding-dev-setup/generalgit clone --depth 1 https://github.com/AndreasKarz/Vibe-Coding-Dev-SetupWhat 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.01096 | $0.01096 |
| Opus 5 | $0.00548 | $0.00548 |
| Sonnet 5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
Vibe-Coding-Dev-Setup general.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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 99 lines · 1,096 tokens per session scan A ffb1716712f1
Vibe-Coding-Dev-Setup general.instructions.md is an instructions file published in the GitHub repository AndreasKarz/Vibe-Coding-Dev-Setup (7 stars, last pushed 6mo ago), with no licence file. It adds 1,096 tokens to every session, about $0.0055 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-31.
Other instructions, from other repositories
copilot-agents-dojo copilot-instructions.md
Instructions for andreaswasita/copilot-agents-dojo, covering copilot instructions, code standards, typescript (default example), python and java.
copilot-agents-dojo AGENTS.md
Instructions for andreaswasita/copilot-agents-dojo, covering copilot agents dojo — contributor guide, project structure, adding a skill, adding a cli command and testing.
vibe-coding-ai-rules AGENTS.md
Instructions for obviousworks/vibe-coding-ai-rules, covering agents.md - universal ai agent configuration, project overview, tech stack, core technologies and key dependencies.
vibe-coding-ai-rules copilot-instructions.md
Instructions for obviousworks/vibe-coding-ai-rules, covering project overview, tech stack, do not use, core principles and setup commands.
vibe-coding-ai-rules code-style.instructions.md
Instructions for obviousworks/vibe-coding-ai-rules, covering code style standards, naming conventions, formatting, do's and don'ts.
vibe-coding-ai-rules react.instructions.md
Instructions for obviousworks/vibe-coding-ai-rules, covering react patterns, component structure, state management, performance and error handling.