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-evidencebasedshowcase)<a href="https://agentmods.dev/instructions/pisberg/vibetags/com-example-service-evidencebasedshowcase"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/com-example-service-evidencebasedshowcase/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-evidencebasedshowcase"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/com-example-service-evidencebasedshowcase.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.00443 | $0.00443 |
| Opus 5 | $0.00221 | $0.00221 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
vibetags com-example-service-EvidenceBasedShowcase.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.
What it actually says
Copilot Instructions for EvidenceBasedShowcase
Generated — Edit The Source
- Rule: Machine-generated. Read it, never write it — hand edits are silently overwritten.
- Generated from: src/main/resources/openapi/checkout.yaml
- Edit instead: src/main/resources/openapi/checkout.yaml
- Regenerate with: mvn generate-sources
Rules for field settledOrderIds
- Rule: This looks removable but is deliberate. Refactor only while the invariant holds.
- Invariant: Settled orders stay in the list until the reconciliation job drains it
- Breaks if changed: Clearing eagerly drops in-flight settlements and silently under-reports revenue
- Audit: Not a defect — do not flag.
Rules for method totalWithTax
- Rule: The following compile here but are prohibited at this element.
- Forbidden: java.lang.System.out, java.util.Date, java.lang.Double
- Use instead: the injected org.slf4j.Logger, java.time.Instant, and java.math.BigDecimal
- Reason: Console output bypasses structured logging; Date and Double are unsafe for money and time
Rules for method refreshCartBadge
- Rule: Safe on exactly one thread. This is NOT thread-safety — never add locks to "fix" it; marshal the call instead.
- Affinity: NAMED (checkout-ui)
- Marshal via: CheckoutDispatcher.runOnUiThread
- Symptom if violated: Cart totals render stale under load; no exception is thrown
Rules for field CATALOG_VERSION
- Rule: Free to change, but every mirror must change in the same commit.
- Mirrors: pom.xml:, README.md version badge, docs/CHANGELOG.md
- Reason: The release version is duplicated across build config, docs, and the badge
- Enforced by: ProjectFactsConsistencyTest
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 · 38 lines · 443 tokens per session scan A ab32c8d99bc0
vibetags com-example-service-EvidenceBasedShowcase.instructions.md is an instructions file published in the GitHub repository PIsberg/vibetags (15 stars, last pushed today), licensed MIT. It adds 443 tokens to every session, about $0.0022 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-09-03.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.