Borrowing it
Nothing to install: this file belongs to visus-mcp/visus-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.
curl -O https://raw.githubusercontent.com/visus-mcp/visus-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/visus-mcp/visus-mcpWrote 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/visus-mcp/visus-mcp/claude-md)<a href="https://agentmods.dev/instructions/visus-mcp/visus-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/visus-mcp/visus-mcp/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.00715 | $0.00715 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
visus-mcp 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visus project conventions
Non-negotiable rules
- No secrets in code, env vars, logs, or git. Secrets Manager only.
- No * in IAM resource ARNs. Explicit ARNs always.
- All infrastructure in IaC (CDK v2). No console changes.
- content_hash computed and verified on every event before DynamoDB write.
- Structured JSON logging on all Lambdas. No stack traces in API responses.
- No test skipping. All tests must pass.
- No Claude/Anthropic outputs used as training data or model outputs.
Schema versioning
- Event schema: shared/schemas/event.schema.json (v1)
- Finding schema: shared/schemas/finding.schema.json (v1, Sprint 2)
- Breaking changes require version bump and schema adapter. See REC-08 in project plan.
Canonical JSON
- All hashing uses shared/canonical-json.ts — never inline JSON.stringify
- Canonical JSON: alphabetically sorted keys, no whitespace, UTF-8
Test floors (minimum, not target)
- Sprint 0: ≥40 unit tests
- Sprint 1: ≥100 unit tests total (60 new)
- Integration tests run against staging, never against production
Naming conventions
- Lambda functions: visus-{name} (e.g. visus-proof-signer)
- DynamoDB tables: visus-{name} (e.g. visus-events)
- Secrets Manager paths: visus/{scope}/{name} (e.g. visus/audit/signing-keypair)
- Environment: VISUS_ENV=staging | production
Language & Runtime
- TypeScript for all Lambda functions and IaC (CDK v2)
- Runtime: Node.js 20.x
- Use Python 3.12 only if a specific library has no TypeScript equivalent
Repository
Ed25519 Keypair Verification
The proof-signer Lambda signs payloads using the Ed25519 private key stored in Secrets Manager. To verify a signature:
# Extract public key from Secrets Manager
aws secretsmanager get-secret-value \
--secret-id visus/audit/signing-keypair \
--region us-east-1 \
--query SecretString --output text > /tmp/priv.pem
openssl pkey -in /tmp/priv.pem -pubout -out /tmp/pub.pem
# Verify a signature
openssl pkeyutl -verify \
-pubin -inkey /tmp/pub.pem \
-rawin -in payload.bin \
-sigfile signature.bin
# Clean up
shred -u /tmp/priv.pem /tmp/pub.pem
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.
- 8d ago First seen · 68 lines · 715 tokens per session scan A 70d98bb8acd2
visus-mcp CLAUDE.md is an instructions file published in the GitHub repository visus-mcp/visus-mcp (1 stars, last pushed 3mo ago), licensed MIT. It adds 715 tokens to every session, about $0.0036 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
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.
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).
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).
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.
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.