What is vibetags copilot-instructions.md?

Generated GitHub Copilot instructions for a project, including files and methods that must not be changed. They also require security review for certain protected code and say the file should not be edited manually.

Use them when Copilot is reviewing or changing the project, particularly around payment processing, security configuration, authentication, and other listed locked files.

They prevent changes that could break payment, authentication, encryption, or compliance-related behavior. They also preserve the source-controlled generation process.

vibetags copilot-instructions.md — Instructions file by PIsberg

Install

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.

Clone the repo

git clone --depth 1 https://github.com/PIsberg/vibetags

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/pisberg/vibetags/copilot-instructions/github.svg)](https://agentmods.dev/instructions/pisberg/vibetags/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/pisberg/vibetags/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/copilot-instructions/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/pisberg/vibetags/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,282 This file is loaded in full into every session.

When invoked 1,282 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review

Origin original No closer match found in the catalogue.

Token cost

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.01282	$0.01282
Opus 5.5	$0.00513	$0.00513
Sonnet 5.5	$0.00256	$0.00256
Haiku 4.5	$0.00128	$0.00128

Measured 1mo ago against content hash 50f1f8a72fcb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

examples/basic/.github/copilot-instructions.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 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-XXXX
com.example.security.SecurityConfig.getEncryptionAlgorithm() - Encryption algorithm tied to compliance requirements (PCI-DSS)
com.example.security.SecurityConfig.getKeyRotationHours() - Key rotation period mandated by company policy
com.example.security.SecurityConfig.getMaxLoginAttempts() - Max login attempts set by security team to prevent brute force
com.example.security.SecurityConfig.validateToken(java.lang.String) - Token validation must match auth server exactly. Changes will break all client authentication
com.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.
com.example.testing.GoldenPayloadFixtures - These byte sequences are the partner's recorded settlement responses. Regenerating or reformatting them makes the suite agree with itself and disagree with production.

Security Audit Requirements

Before suggesting changes to the following files, audit for the listed vulnerabilities:

Read the full file on GitHub · 77 lines

Changes

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.

1mo ago Changed · -31 lines · -184 tokens per session 50f1f8a72fcb
1mo ago Changed · +17 lines · +204 tokens per session 162f62053a74
1mo ago Changed · -468 tokens per session 68e7981eda22
2mo ago First seen · 91 lines · 1,730 tokens per session scan A ea30c281d7d3

Subscribe to this mod's changes

vibetags copilot-instructions.md is an instructions file published in the GitHub repository PIsberg/vibetags (25 stars, last pushed today), licensed MIT. It adds 1,282 tokens to every session, about $0.0051 per session on Opus 5.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.

Java Planning Security ai ai-tools annotation annotations claude

vibetags copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
vibetags copilot-instructions.mdPIsberg/vibetags	Instructions file	25	today	MIT	A	1,282	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode