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/com-example-database-databaseconnectorgit clone --depth 1 https://github.com/PIsberg/vibetagsWhat 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.00112 | $0.00112 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
com-example-database-DatabaseConnector 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 2d 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 DatabaseConnector
Security Audit Requirements
When modifying this element, audit for:
- SQL Injection
- Thread Safety issues
PII / Privacy Guardrails
- Rule: Never log or expose runtime values of these elements.
- Reason: Database credential - never log or include in error messages
- Applies to:
DatabaseConnector.password,DatabaseConnector.username
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.
- 2d ago First seen · 18 lines · 112 tokens per session scan A a1d5021182b2
com-example-database-DatabaseConnector is an instructions file published in the GitHub repository PIsberg/vibetags (14 stars, last pushed 3d ago), licensed MIT. It adds 112 tokens to every session, about $0.0006 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
autotask-mcp dev_workflow.instructions.md
Guide for using Taskmaster to manage task-driven development workflows.
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
foggy-data-mcp-bridge-python CLAUDE.md
Instructions for foggy-projects/foggy-data-mcp-bridge-python, covering foggy data mcp bridge — python, 快速启动, 安装依赖, 运行测试 and 启动 mcp 服务（连接 docker mysql）.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.
genesis-architect CLAUDE.md
Claude Code instructions for maioio/genesis-architect, covering genesis architect - claude code instructions, project structure, how this skill works, development workflow and key constraints (enforced in skill.md).