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/pisberg/vibetags/copilot-instructionsgit clone --depth 1 https://github.com/PIsberg/vibetagsWrote 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/pisberg/vibetags/copilot-instructions)<a href="https://agentmods.dev/instructions/pisberg/vibetags/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/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 | $0.01730 | $0.01730 |
| Opus 5 | $0.00865 | $0.00865 |
| Sonnet 5 | $0.00346 | $0.00346 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
vibetags 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
Generated by VibeTags | https://github.com/PIsberg/vibetags
AUTO-GENERATED BY VIBETAGS. Do not edit manually.
Locked Files — DO NOT MODIFY
Do not suggest changes to the following files:
com.example.payment.PaymentProcessor- Tied to legacy database schema v2.3. Changes will break production payment processing. Contact the payments team before modifying.com.example.security.SecurityConfig- CRITICAL: Security configuration managed by DevOps team. Any changes require security review and approval ticket SEC-XXXXcom.example.security.SecurityConfig.getEncryptionAlgorithm()- Encryption algorithm tied to compliance requirements (PCI-DSS)com.example.security.SecurityConfig.getKeyRotationHours()- Key rotation period mandated by company policycom.example.security.SecurityConfig.getMaxLoginAttempts()- Max login attempts set by security team to prevent brute forcecom.example.security.SecurityConfig.validateToken(java.lang.String)- Token validation must match auth server exactly. Changes will break all client authenticationcom.example.service.OrderService.calculateTax(java.lang.String,double)- Tax calculation uses Avalara API integration. Credentials and endpoint configuration managed by finance team.com.example.service.OrderService.processPayment(java.lang.String,double)- Payment processing uses Stripe API v2024.10. Changes require PCI compliance review.com.example.service.OrderService.validateOrder(java.util.Map<java.lang.String,java.lang.Object>)- Order validation implements 47 business rules. Last changed in Q2 2024 after 3-month testing cycle. DO NOT MODIFY without running full test suite.
Security Audit Requirements
Before suggesting changes to the following files, audit for the listed vulnerabilities:
com.example.database.DatabaseConnector- Required Checks: SQL Injection, Thread Safety issues
Ignored Elements
Do not reference or suggest changes to the following:
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.
- 5d ago First seen · 91 lines · 1,730 tokens per session scan A ea30c281d7d3
vibetags copilot-instructions.md is an instructions file published in the GitHub repository PIsberg/vibetags (15 stars, last pushed yesterday), licensed MIT. It adds 1,730 tokens to every session, about $0.0086 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
tachyon GEMINI.md
Gemini CLI instructions for kpavlov/tachyon: In repositories indexed by CodeGraph (a .codegraph/ directory exists at the repo root), reach for it BEFORE grep/find or reading files when you need to understand or locate code.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.
AmbyKit CLAUDE.md
Claude Code instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.
mcp-execution mcp-wasm-runtime.instructions.md
Instructions for bug-ops/mcp-execution, covering copilot instructions: mcp-wasm-runtime, security - critical, security principles, security configuration and host function safety.
mcp-ai-wpoos CLAUDE.md
Claude Code instructions for nvdigitalsolutions/mcp-ai-wpoos, covering nv oos (open operator system) — claude code context, related files, what this is, php compatibility — critical and naming conventions.
skillsync-mcp CLAUDE.md
Instructions for adityasugandhi/skillsync-mcp, covering claude.md, project overview, development commands, architecture and key files.