vibecompass-mcp: Instructions file for Codex

AGENTS.md

vibecompass-mcp AGENTS.md is an instructions file for Codex, OpenCode from jack-whimvy/vibecompass-mcp. It costs 255 tokens per session, scanned A, original, MIT.

Repository instructions for working on VibeCompass MCP, a local client and server that gives AI tools access to project context. They describe the repository, commands, environment settings, and related documentation.

In plain words
What is it for?
Building, running, and maintaining the VibeCompass MCP repository, including its local, hosted, and hybrid operating modes.
Why use it?
They help keep tool contracts, error handling, project context, and TypeScript conventions consistent while the code is changed.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md.

This is jack-whimvy/vibecompass-mcp's own configuration. It tells Codex and OpenCode how to work on vibecompass-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vibecompass-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jack-whimvy/vibecompass-mcp. 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/jack-whimvy/vibecompass-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/jack-whimvy/vibecompass-mcp

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.

agentmods badge for vibecompass-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jack-whimvy/vibecompass-mcp/agents-md.svg)](https://agentmods.dev/instructions/jack-whimvy/vibecompass-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/jack-whimvy/vibecompass-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jack-whimvy/vibecompass-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 255 This file is loaded in full into every session.
When invoked 255 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00255 $0.00255
Opus 5 $0.00128 $0.00128
Sonnet 5 $0.00051 $0.00051
Haiku 4.5 $0.00026 $0.00026

Measured 7d ago against content hash aa9c04a258b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

vibecompass-mcp 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 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.

AGENTS.md · 31 lines

What it actually says

VibeCompass MCP

Read ../vibecompass-docs/CLAUDE.md first for project context and session continuity.

Repo Purpose

This package is the local MCP client/server layer that exposes VibeCompass context to AI tools over stdio.

Working Rules

  • Keep tool contracts aligned with vibecompass-app /api/mcp/* endpoints
  • Read tools should stay resilient and never hard-fail the user session
  • Write tools should surface failures clearly
  • Preserve TypeScript ESM / NodeNext conventions

Commands

  • npm run build
  • npm run dev
  • npm run start

Important Context

  • Runtime env:
    • hosted mode: VIBECOMPASS_API_KEY, optional VIBECOMPASS_API_URL
    • local read mode: VIBECOMPASS_ROOT
    • hybrid mode: if both are set, read tools use the local root while write tools and hosted conflict reads stay enabled through the API client
  • Current architecture and behavior decisions live in:
    • ../vibecompass-docs/decisions/mcp-server.md
    • ../vibecompass-docs/architecture/mcp-server/
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.

  1. 7d ago First seen · 31 lines · 255 tokens per session scan A aa9c04a258b8

Subscribe to this mod's changes

vibecompass-mcp AGENTS.md is an instructions file published in the GitHub repository jack-whimvy/vibecompass-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 255 tokens to every session, about $0.0013 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-31.

Related

Other instructions, from other repositories

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens