Borrowing it
Nothing to install: this file belongs to quanghoangf/vibedoc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/quanghoangf/vibedoc/main/CLAUDE.mdgit clone --depth 1 https://github.com/quanghoangf/vibedocWrote 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/quanghoangf/vibedoc/claude-md)<a href="https://agentmods.dev/instructions/quanghoangf/vibedoc/claude-md"><img src="https://agentmods.dev/badge/instructions/quanghoangf/vibedoc/claude-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.
<a href="https://agentmods.dev/instructions/quanghoangf/vibedoc/claude-md"><img src="https://agentmods.dev/badge/instructions/quanghoangf/vibedoc/claude-md.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.03003 | $0.03003 |
| Opus 5.5 | $0.01201 | $0.01201 |
| Sonnet 5.5 | $0.00601 | $0.00601 |
| Haiku 4.5 | $0.00300 | $0.00300 |
Grade A, and why
vibedoc CLAUDE.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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeDoc — Agent Instructions
What this is
A Next.js 16 app that serves as both a kanban/docs viewer for developers AND an MCP server for AI coding agents. One running process, two clients. The UI and the AI agent share the same API layer.
Stack
- Framework: Next.js 16 (App Router, TypeScript)
- Styling: Tailwind CSS 4 (CSS-first config in
globals.css) — dark theme, no component library - Runtime: Node.js 18+ (server-side file system access)
- MCP transport: HTTP JSON-RPC 2.0 at
/api/mcp - Real-time: Server-Sent Events at
/api/events - Data: File system only — no database. Reads
.mdfiles from target project.
Repo structure
src/
app/
page.tsx ← Main UI shell (single-page, client component)
layout.tsx ← Root layout
globals.css ← Tailwind + markdown prose styles
(app)/roadmap/page.tsx ← Roadmap page (roadmap.sh-style, React Flow)
(app)/graph/page.tsx ← Whole-repo doc link graph (React Flow, force layout)
(app)/chat/page.tsx ← All agent chats: list · conversation · epic/task context
(app)/manual-tests/page.tsx ← Test review: task list (Needs you/Failed/Passed/No run) + run replay, checklist, review; Evidence view (?view=evidence)
api/
mcp/route.ts ← MCP JSON-RPC endpoint (AI connects here)
events/route.ts ← SSE stream (real-time browser updates)
tasks/route.ts ← Task CRUD
docs/route.ts ← Doc list/read/search
memory/route.ts ← MEMORY.md read/write
decisions/route.ts ← ADR creation
activity/route.ts ← Activity log read
projects/route.ts ← Multi-project discovery
summary/route.ts ← Combined project status
chat/route.ts ← Agent chat turn: spawns `claude -p` (local login), VibeDoc MCP tools only
conversations/route.ts ← Saved agent chats (.vibedoc/chats/<id>.json)
tasks/manual-tests/route.ts ← Tick a task's manual test item
tasks/review/route.ts ← Approve / send back a task in review
tasks/[id]/evidence/route.ts ← A task's evidence doc (checklist × kept runs), ?run= for an older run
tasks/run/route.ts ← Run a task's spec from VibeDoc (one per project, live SSE `test_run`); run/cancel stops it
suite/run/route.ts ← Regression suite: every done task's spec in one Playwright run (SSE `suite_run`); shares the run lock
roadmap/* ← Roadmap list + create/update/delete/layout
llms.txt/route.ts ← /llms.txt: docs index for any agent, built from the files (R087)
md/[...path]/route.ts ← /md/<path>: one doc as text/markdown, agent view (R087)
proxy.ts ← /docs?doc= with Accept: text/markdown → /md/<path>
components/
roadmap/ ← Roadmap canvas, nodes, editor
context/
ChatContext.tsx ← Agent chats store (modal, /chat page, sidebar, roadmap/board markers)
lib/
core.ts ← ALL file system logic (shared by API routes + MCP)
events.ts ← In-process SSE event bus (singleton)
desktop/ ← Desktop app (R111/R112): Electron shell (own package.json + lockfile, exact electron pin) around the running hub, its update check and installers (scripts/dist.mjs, electron-builder.yml); docs/desktop-app.md
bin/ ← The `vibedoc` CLI, plain JS shipped unbuilt: start/stop/status/login (R109/R110), address + hub (R080/R100), supervisor
.github/workflows/ ← ci, release (semantic-release → npm, site, desktop, Homebrew), desktop (installers per OS), site
plugin/ ← Claude Code plugin `vibedoc`: skills/{roadmap,breakdown,work,next} → /vibedoc:<name>; the chat reads roadmap + breakdown
.claude-plugin/marketplace.json ← marketplace for `/plugin install vibedoc@vibedoc`
docs/ ← VibeDoc's own documentation (this project)
docs/specs/ ← Capability specs (R066): one <capability>.md per capability, requirements + WHEN/THEN scenarios
plans/tasks/ ← Development tasks
plans/roadmap/ ← Roadmap items (R*.md) + layout.json
memory/MEMORY.md ← Session handoff
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.
- 7d ago Changed · +3 lines · +614 tokens per session bccb77dc5253
- 11d ago Changed · +117 tokens per session b2099c303f2e
- 14d ago Changed · +1 lines · +115 tokens per session 02d2328bb178
- 20d ago Changed · +3 lines · +362 tokens per session 1284bfba7a46
- 21d ago Changed · +6 lines · +316 tokens per session e17c212c10e5
- 22d ago Changed · +1 lines · +153 tokens per session 459da5a3b344
- 24d ago Changed · +1 lines · +119 tokens per session a2e01315ef9a
- 26d ago Changed · +3 lines · +166 tokens per session 0f20a453b600
- 28d ago Changed · +4 lines · +84 tokens per session 95801f871c22
- 29d ago First seen · 81 lines · 957 tokens per session scan A 1a57df26cd96
vibedoc CLAUDE.md is an instructions file published in the GitHub repository quanghoangf/vibedoc (8 stars, last pushed 4d ago), licensed MIT. It adds 3,003 tokens to every session, about $0.0120 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-31.
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.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.