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.
git 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/com-example-service-inventoryservice)<a href="https://agentmods.dev/instructions/pisberg/vibetags/com-example-service-inventoryservice"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/com-example-service-inventoryservice/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.
<a href="https://agentmods.dev/instructions/pisberg/vibetags/com-example-service-inventoryservice"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/com-example-service-inventoryservice.svg" alt="Reviewed on agentmods" width="80" 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.00367 | $0.00367 |
| Opus 5.5 | $0.00147 | $0.00147 |
| Sonnet 5.5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
vibetags com-example-service-InventoryService.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.
What it actually says
Copilot Instructions for InventoryService
Context & Focus
- Focus: Maintain inventory consistency across concurrent requests. All stock updates must be atomic.
- Avoid: Non-atomic read-modify-write sequences, unsynchronized shared state
Rules for field customerId
- Rule: Never log or expose runtime values of this element.
- Reason: Customer identifiers linked to purchase history — PII under GDPR
Rules for method releaseReservation
- Sensitivity: High
- Note: Must be called as the exact inverse of reserveStock. Pair changes to both methods together.
Rules for method reserveStock
- Sensitivity: Critical
- Note: Reservation logic handles concurrent requests via optimistic locking. Took 18 months to get right under high load — do not refactor without running the full concurrency test suite.
Performance Constraints
- Rule: Optimal complexity required. O(n^2) is forbidden on hot paths.
Rules for method bulkRestock
- Constraint: Must process 10 000 SKU updates/second. O(n) acceptable; O(n log n) only if unavoidable; O(n²) is forbidden.
Rules for method getAvailableStock
- Constraint: O(1) lookup required. Must complete in <2ms p99. No database calls permitted; reads from in-memory cache only.
Rules for method sendLowStockAlert
- Flag: 'inventory.push-alerts.enabled' (default: false)
- Rule: This code is gated behind a feature flag. Preserve the flag check. Never assume the flag is always active.
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 First seen · 37 lines · 367 tokens per session scan A f6f321ec825b
vibetags com-example-service-InventoryService.instructions.md is an instructions file published in the GitHub repository PIsberg/vibetags (25 stars, last pushed yesterday), licensed MIT. It adds 367 tokens to every session, about $0.0015 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-09-03.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).