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/giauphan/codeatlas-platform/claude-mdgit clone --depth 1 https://github.com/giauphan/codeatlas-platformWrote 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/giauphan/codeatlas-platform/claude-md)<a href="https://agentmods.dev/instructions/giauphan/codeatlas-platform/claude-md"><img src="https://agentmods.dev/badge/instructions/giauphan/codeatlas-platform/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 | $0.01641 | $0.01641 |
| Opus 5 | $0.00821 | $0.00821 |
| Sonnet 5 | $0.00328 | $0.00328 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
codeatlas-platform 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 3d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — CodeAtlas Platform
Start here when joining this repository. This file is the operating guide for AI assistants implementing, debugging, reviewing, or maintaining CodeAtlas Platform.
Remember: You're an amazing performance engineer, making things lightning fast. But speed without correctness is useless. Measure, optimize, verify.
1. What This Project Is
CodeAtlas Platform is an AI-powered codebase-intelligence backend. It analyzes software projects, maps AST and dependency relationships, and makes that knowledge available to AI tools and clients through MCP and HTTP APIs.
Primary capabilities:
- Analyze source code, entities, dependencies, and feature flows.
- Provide MCP tools for codebase exploration and AI-assisted development.
- Store and retrieve semantic project knowledge through Dream, Genome, and Immune services.
- Persist codebase and memory data locally with SQLite and
sqlite-vec. - Support SQLite by default with optional PostgreSQL configuration.
- Integrate the dashboard with Firebase services where required.
- Expose Express.js HTTP routes and MCP server endpoints.
2. Architecture Map
src/
├── presentation/ # Express routes, MCP server, request/response contracts
├── services/ # Domain and application logic
├── repositories/ # SQLite, PostgreSQL, and other persistence access
├── database/ # Database initialization, adapters, connections
├── middleware/ # Express middleware and error handling
├── utils/ # Shared utilities
└── env.ts # Validated environment configuration
Follow the dependency direction:
presentation → services → repositories/database
- Keep HTTP and MCP concerns in
presentation. - Keep business rules and orchestration in
services. - Keep SQL and database-specific behavior in
repositoriesanddatabase. - Do not move database logic into routes or route-specific logic into services without a clear reason.
3. First Steps in Every New Session
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.
- 3d ago First seen · 188 lines · 1,641 tokens per session scan A eea5e0b0dc1a
codeatlas-platform CLAUDE.md is an instructions file published in the GitHub repository giauphan/codeatlas-platform (11 stars, last pushed 4d ago), licensed MIT. It adds 1,641 tokens to every session, about $0.0082 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-30.
Other instructions, from other repositories
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.