What is vibeusage AGENTS.md?

Project instructions for AI assistants covering proposals, repository structure, SQLite usage, and rules for keeping a repository map up to date. It also explains when to read the project's OpenSpec instructions before coding.

Use it before planning, proposing, or making changes that affect architecture, data flow, public interfaces, or multiple modules.

It prevents agents from missing required project guidance or crossing module boundaries without checking them. The repository map helps identify the right entry points and affected areas.

How victorGPT/vibeusage configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to victorGPT/vibeusage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/victorGPT/vibeusage/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/victorGPT/vibeusage

Made for: Codex, OpenCode.

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/victorgpt/vibeusage/agents-md/github.svg)](https://agentmods.dev/instructions/victorgpt/vibeusage/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/victorgpt/vibeusage/agents-md"><img src="https://agentmods.dev/badge/instructions/victorgpt/vibeusage/agents-md/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/victorgpt/vibeusage/agents-md"><img src="https://agentmods.dev/badge/instructions/victorgpt/vibeusage/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,320 This file is loaded in full into every session.

When invoked 2,320 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.

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.02320	$0.02320
Opus 5.5	$0.00928	$0.00928
Sonnet 5.5	$0.00464	$0.00464
Haiku 4.5	$0.00232	$0.00232

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

Security

Grade A, and why

vibeusage AGENTS.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 2mo 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.

AGENTS.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenSpec Instructions

These instructions are for AI assistants working in this project.

Always open @/openspec/AGENTS.md when the request:

Mentions planning or proposals (words like proposal, spec, change, plan)
Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
Sounds ambiguous and you need the authoritative spec before coding

Use @/openspec/AGENTS.md to learn:

How to create and apply change proposals
Spec format and conventions
Project structure and guidelines

Keep this managed block so 'openspec update' can refresh the instructions.

仓库站点地图规则

非 trivial 变更前先阅读 docs/repo-sitemap.md，用它确定当前模块边界、入口文件与首读路径。
当变更影响模块边界、跨模块数据流、公共接口、或首选入口文件时，必须同步更新 docs/repo-sitemap.md。
渐进式披露：先读站点地图里的顶层目录和目标模块小节，只在依赖仍不清楚时再扩大阅读范围。
小改动聚焦单模块；中等改动扩展到相邻模块；跨模块/数据流改动沿着站点地图列出的路径逐步展开。

站点地图执行边界（强制 vs 可选）

强制（必须读 + 更新站点地图）

架构变更或系统边界调整
数据流/存储/同步路径变化
公共接口或契约改变（API、事件、数据模型）
跨模块耦合关系调整
模块首选入口文件或作者路径变化

可选（允许跳过站点地图更新）

局部 bugfix（不影响模块边界/数据流）
纯文案/样式/格式类改动
孤立脚本修补（不进入核心流程）

最小摩擦执行规则

变更前判断是否触发“强制”条件
触发则先读并在结束后更新 docs/repo-sitemap.md；不触发可跳过
提交信息或 PR 描述可附一句：Repo sitemap: updated 或 Repo sitemap: not required

SQLite 使用习惯（渐进式披露）

定位顺序：先用 docs/repo-sitemap.md 缩小范围（模块/路径前缀），再用 SQLite 精确查询。
查询原则：只输出最小结果集（几十/几百行以内），禁止全量导出。
模板优先：使用 docs/graph/sql-templates.md 的固定 SQL，避免手写出错。
目标定位：SQLite 仅负责“符号级事实定位”，输出结果再交给 AI。

OpenSpec 使用范围

默认使用 skill 工作流，不强制走 OpenSpec。
仅在以下“重大模块”场景触发 OpenSpec：外部集成、跨模块核心流程、DB schema 变更、安全/权限边界变化、破坏性变更。

文案规则（Copy Registry）

本项目页面上所有展示文字必须来自 dashboard/src/content/copy.csv。
任何文案改动必须汇总到文案表，不允许在组件内新增/修改硬编码文本。
文案表与项目官网内容必须双向同步：官网改动需回写文案表，文案表更新需同步到官网。

回归用例要求

每次提交必须执行回归用例（至少覆盖本次变更相关路径），并记录执行命令与结果。

PR 预检与风险层门禁

PR 模板必须填写 Affected Modules / Contracts、Validation 与 Risk Flags；跨模块变更需附 repo sitemap evidence（更新说明或受影响小节）。
若 Risk Flags 勾选任一项，必须补全 Risk Addendum（Rules / Invariants、Boundary Matrix ≥ 3、Evidence）。
若勾选 Public exposure / share links / unauthenticated access，必须补全 Public Exposure Addendum。
Reviewer Context 仅供 reviewer / AI 复审参考，不属于硬门禁。
CI 会执行 node scripts/ops/pr-risk-layer-gate.cjs；在 CI 中优先读取 live PR body，event payload 仅作为 fallback；本地可用 --body-file 预检。
详细流程见 docs/ops/pr-review-preflight.md。

Read the full file on GitHub · 152 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.

2mo ago First seen · 152 lines · 2,320 tokens per session scan A 89e831d625f8

Subscribe to this mod's changes

vibeusage AGENTS.md is an instructions file published in the GitHub repository victorGPT/vibeusage (130 stars, last pushed 3mo ago), licensed MIT. It adds 2,320 tokens to every session, about $0.0093 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.

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

vibeusage: Instructions file for Codex