Borrowing it
Nothing to install: this file belongs to AntaresQAQ/VoxMesh. 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/AntaresQAQ/VoxMesh/main/CLAUDE.mdgit clone --depth 1 https://github.com/AntaresQAQ/VoxMeshWrote 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/antaresqaq/voxmesh/claude-md)<a href="https://agentmods.dev/instructions/antaresqaq/voxmesh/claude-md"><img src="https://agentmods.dev/badge/instructions/antaresqaq/voxmesh/claude-md.svg" alt="Measured on agentmods" 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.00447 | $0.00447 |
| Opus 5 | $0.00224 | $0.00224 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
VoxMesh 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.
What it actually says
Claude Code Instructions
Before planning, editing, or running implementation commands, read and follow:
The linked documents are authoritative. In particular:
- All repository content and code comments must be in English.
- User conversation may be in English or Chinese.
- Functional behavior must be discussed and explicitly confirmed before implementation.
- Changes must remain within the confirmed scope.
- Never modify
maindirectly; work on a dedicated<type>/<short-description>branch created from the latestmain. - All changes must reach
mainthrough a reviewed pull request with passing required CI. - Commit messages and PR titles must use an English prefix such as
feat:,fix:, ordocs:. - Split unrelated concerns and different change types into focused commits.
- Complete unit, integration where applicable, and end-to-end tests are required for every functional change.
- Implementation changes must include thorough English developer documentation for behavior, configuration, architecture, failures, and extension points.
- Public contracts and non-obvious or security-sensitive logic require concise JSDoc or reasoning comments; comments must explain why rather than narrate syntax.
- Web Console pages must be composed from small, single-purpose components rather than monolithic files.
- Every new or changed Web Console component must include focused behavioral unit tests.
- Every Web Console change must meet WCAG 2.2 AA and verify keyboard, focus, semantics, forms, responsive zoom, and contrast across English/Chinese and Light/Dark themes.
- jsx-a11y linting and representative Playwright axe scans are required; accessibility failures must not be silently suppressed.
- Applicable format, lint, type-check, test, and production-build checks must pass.
- Never commit, push, create or merge a pull request, or perform any other Git remote operation without explicit confirmation for that exact operation.
- Preserve existing user work, secrets, data, API compatibility, and the platform-independent architecture.
If requirements or instructions are ambiguous or conflicting, pause before implementation and ask the user to clarify.
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 First seen · 31 lines · 447 tokens per session scan A 2899594967a3
VoxMesh CLAUDE.md is an instructions file published in the GitHub repository AntaresQAQ/VoxMesh (1 stars, last pushed 3d ago), licensed MIT. It adds 447 tokens to every session, about $0.0022 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
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.
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.
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 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).
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.