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/bhvbhushan/vibecop/copilot-instructionsgit clone --depth 1 https://github.com/bhvbhushan/vibecopWrote 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/instructions/bhvbhushan/vibecop/copilot-instructions)<a href="https://agentmods.dev/instructions/bhvbhushan/vibecop/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/bhvbhushan/vibecop/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>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.00032 | $0.00032 |
| Opus 5 | $0.00016 | $0.00016 |
| Sonnet 5 | $0.00006 | $0.00006 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
vibecop copilot-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 6d 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
vibecop
After every code edit, run npx vibecop scan --diff HEAD --format agent and fix any findings before proceeding.
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.
- 6d ago First seen · 4 lines · 32 tokens per session scan A ecfb0612b650
vibecop copilot-instructions.md is an instructions file published in the GitHub repository bhvbhushan/vibecop (57 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session, about $0.0002 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
arbiterx CLAUDE.md
Instructions for NeelPrime/arbiterx, covering arbiterx engineering rules, setup, rules (always enforced), never generate and quality gate.
arbiterx AGENTS.md
Instructions for NeelPrime/arbiterx, covering arbiterx — engineering discipline for ai code generation, before writing code, the 10 rules (always enforce), never generate and after writing.
arbiterx copilot-instructions.md
Instructions for NeelPrime/arbiterx, covering engineering rules (arbiterx), required, forbidden and prefer.
archguardian CLAUDE.md
Instructions for ysfAskri/archguardian, covering archguardian, project structure, build & test, key conventions and available skills.
archguardian copilot-instructions.md
Instructions for ysfAskri/archguardian, covering archguardian, project structure, build & test, key conventions and cli commands.
logic-lens GEMINI.md
Instructions for hyhmrright/logic-lens, covering logic-lens — developer guide (gemini cli), invoking skills, installation, project layout and key conventions.