Borrowing it
Nothing to install: this file belongs to bryankthompson/chroma-mcp-custom. 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/bryankthompson/chroma-mcp-custom/main/CLAUDE.mdgit clone --depth 1 https://github.com/bryankthompson/chroma-mcp-customWrote 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/bryankthompson/chroma-mcp-custom/claude-md)<a href="https://agentmods.dev/instructions/bryankthompson/chroma-mcp-custom/claude-md"><img src="https://agentmods.dev/badge/instructions/bryankthompson/chroma-mcp-custom/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/bryankthompson/chroma-mcp-custom/claude-md"><img src="https://agentmods.dev/badge/instructions/bryankthompson/chroma-mcp-custom/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.01499 | $0.01499 |
| Opus 5 | $0.00749 | $0.00749 |
| Sonnet 5 | $0.00300 | $0.00300 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
chroma-mcp-custom 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 9d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chroma MCP Server Development Guide
Project Status Documentation
Current Project Status Reference
Authoritative Source: PROJECT_STATUS.md contains the definitive current state including:
- Current Phase Status: Migration progress, completion percentages, and active development focus
- Priority Rankings: Immediate next actions, current development tasks, and upcoming phases
- Legacy Integration Results: Documentation consolidation outcomes and system integration status
- Deployment Status: Service health, environment configurations, and production readiness
- Performance Metrics: Memory system health, optimization achievements, and reliability statistics
Status Management Commands
Session Management:
/brainpod-PROJECT-STATUS-LOAD- Load current project status for session context/brainpod-PROJECT-STATUS-UPDATE- Update project status with recent progress/brainpod-init-quick-status-to-claude-link- Sync CLAUDE.md with PROJECT_STATUS.md references
Development Workflow:
- Session Start: Use
/brainpod-PROJECT-STATUS-LOADto understand current priorities - Development Work: Follow immediate next actions from PROJECT_STATUS.md
- Progress Update: Use
/brainpod-PROJECT-STATUS-UPDATEto document completion - Context Preservation: Maintain living document synchronization
Status Integration Benefits
- Eliminates Duplication: CLAUDE.md provides development guidance while PROJECT_STATUS.md tracks current state
- Session Continuity: Claude can immediately understand project context and priorities
- Living Documentation: Status files automatically track progress and maintain audit trails
- Cross-Project Consistency: Standardized status format across all projects
Development Environment
WSL Integration
This project runs in WSL2 with Docker containers. Key development files:
- Wrapper Script:
/home/bryan/run-chroma-mcp.sh- Primary MCP server access - Container Access: Uses
docker execfor MCP protocol communication - Port Configuration: See PROJECT_STATUS.md for current port allocations
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.
- 9d ago First seen · 189 lines · 1,499 tokens per session scan A e476d9edebc1
chroma-mcp-custom CLAUDE.md is an instructions file published in the GitHub repository bryankthompson/chroma-mcp-custom (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 1,499 tokens to every session, about $0.0075 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.