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/basic-bit/vrchat-mcp/agents-mdgit clone --depth 1 https://github.com/BASIC-BIT/vrchat-mcpWhat 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.01604 | $0.01604 |
| Opus 5 | $0.00802 | $0.00802 |
| Sonnet 5 | $0.00321 | $0.00321 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
vrchat-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 yesterday.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
This repo uses linting, typechecking, and tests to validate changes.
Guidance for coding agents:
- After significant code changes (or at the end of a work loop), run
npm run check. - If you need just one step, use
npm run lint,npm run typecheck, ornpm test. - After making a change, run at least one relevant targeted test (or add/edit one) and confirm it passes before reporting back.
- For PR review workflow: before pushing any new commits, respond to each open review comment (reply or reaction) and resolve the thread.
- Claude reviews non-draft, non-fork PRs automatically and rewrites one sticky comment per PR. The review job uses GitHub OIDC to retrieve BASIC's canonical Claude OAuth token from AWS Secrets Manager; there is no repository copy to rotate. Calibration lives in
REVIEW.md; add theskip-claude-reviewlabel to opt a PR out. - Keep stdout reserved for MCP protocol; log to stderr only.
- Config defaults live in
src/config/defaults.json; override viaVRCHAT_MCP_CONFIG_FILE(env overrides still supported). - Prefer the local harness over Codex MCP hosting for dev iteration:
npm run mcp:loginto authenticate (keeps the server alive while you log in).npm run mcp:status,npm run mcp:logout,npm run mcp:list-tools,npm run mcp:call.- The harness defaults cookie storage to
file. Override via config JSON or env vars if needed. - Use
VRCHAT_MCP_SERVER_COMMAND/VRCHAT_MCP_SERVER_ARGSto switch betweentsx src/index.tsand builtdist/bin/cli.js.
- Write tools are enabled by default. Use
writes.allow=falsein config, orVRCHAT_MCP_ALLOW_WRITES=false, when a test or run must be read-only. - Regenerate tool catalog docs after spec updates:
npm run generate:tools-docs. - Regenerate VRChat OpenAPI schemas after spec updates:
npm run generate:schemas(updatessrc/generated/vrchat-schemas.ts; do not edit manually). - Regenerate mock test schemas after spec tweaks:
npm run generate:test-schemas(updatestest/generated/mock-schemas.ts; do not edit manually). specs/vrchat-openapi.yamlis the community spec, not VRChat's, and drifts from the live API continuously.docs/spec-drift.mdlogs divergences we have observed so nobody re-investigates them — it is a record, not an authority; the live API is the source of truth. Read it before trusting a spec constraint, re-verify any entry you are about to depend on for a substantive change, and add an entry whenever you find a new divergence. Fix drift inscripts/postprocess-schemas.ts, not in the spec: the spec file is gitignored, so edits there are local-only and vanish on a fresh clone.
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.
- yesterday First seen · 84 lines · 1,604 tokens per session scan A 0303a03fcb13
vrchat-mcp AGENTS.md is an instructions file published in the GitHub repository BASIC-BIT/vrchat-mcp (2 stars, last pushed 8d ago), licensed MIT. It adds 1,604 tokens to every session, about $0.0080 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.
Other instructions, from other repositories
now-sdk-ext-mcp CLAUDE.md
Instructions for sonisoft-cnanda/now-sdk-ext-mcp, covering now-sdk-ext-mcp, project overview, architecture, directory structure and sibling projects.
mistral-mcp CLAUDE.md
Instructions for Swih/mistral-mcp, covering claude.md — mistral-mcp, 1. identité du projet, 2. règles dures (ne pas transgresser), 3. layout & responsabilités and 4. conventions de code.
velog_mcp AGENTS.md
Instructions for seongwon030/velog_mcp, covering agents.md, 프로젝트 개요, 스택과 명령어, 아키텍처 and api와 동작 메모.
mcp-local-llm AGENTS.md
Instructions for aplaceforallmystuff/mcp-local-llm, covering agents.md - mcp-local-llm, tech stack, architecture, development commands and environment variables.
toon-memory AGENTS.md
Instructions for LuiggiVal08/toon-memory, covering agents.md, build & verify, architecture, smarter memory pattern and visual memory pattern.
miftah AGENTS.md
Instructions for mohanagy/miftah, covering miftah agent instructions, madar, codex cli profile and release protocol.