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/aegntic/cldcde/claude-mdgit clone --depth 1 https://github.com/aegntic/cldcdeWrote 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/aegntic/cldcde/claude-md)<a href="https://agentmods.dev/instructions/aegntic/cldcde/claude-md"><img src="https://agentmods.dev/badge/instructions/aegntic/cldcde/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.00605 | $0.00605 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
cldcde 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
Development
bun dev- Start development server with hot reloadbun build- Build frontend for productionbun start- Run production serverbun test- Run tests (no tests implemented yet)
Database
- Neo4j must be running locally or configured via environment variables
- Database initialization: Create constraints and sample data by running queries in
src/db/neo4j.ts
Architecture
Backend Structure
The backend uses Hono framework on Bun runtime with a modular API design:
-
API Routes (
src/api/): Each module exports route handlers- Auth endpoints handle JWT-based authentication
- Extensions and MCP endpoints manage platform resources
- All routes use Zod for validation
-
Database (
src/db/neo4j.ts): Neo4j graph database- Graph model: Users -> Extensions/MCPs with relationships (CREATED, INSTALLED, RATED)
- Connection pool management with graceful fallback
- Cypher queries for all database operations
-
Authentication (
src/auth/): JWT tokens with bcrypt password hashing- Middleware in
server.tsprotects routes - Token verification for protected endpoints
- Middleware in
Frontend Structure
React application with terminal-inspired UI:
-
Components (
frontend/src/components/): Modular React components- Theme-aware components using styled-components
- Terminal aesthetic with ASCII art and monospace fonts
-
Theming (
frontend/src/styles/themes.ts): Multiple terminal themes- Theme context provider for global theme management
- Themes: Default, Dracula, Monokai, Solarized, Nord, Gruvbox
-
State Management: React Context API for auth and theme state
Key Technical Decisions
- Bun over Node.js: Faster runtime with built-in TypeScript support
- Hono over Express: Lightweight, edge-ready framework
- Neo4j over SQL: Graph relationships perfect for user-extension connections
- styled-components: Dynamic theming with CSS-in-JS
- Zod validation: Type-safe runtime validation for APIs
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.
- 5d ago First seen · 67 lines · 605 tokens per session scan A c90d72581966
cldcde CLAUDE.md is an instructions file published in the GitHub repository aegntic/cldcde (11 stars, last pushed 8d ago), licensed MIT. It adds 605 tokens to every session, about $0.0030 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
pi-coding-agent-forge AGENTS.md
AGENTS.md instructions for Firstp1ck/pi-coding-agent-forge, covering repository documentation rules, documentation goal, required documentation layers, readme.md — human guide and technical.md — advanced user reference.
nutrition-mcp CLAUDE.md
Claude Code instructions for akutishevsky/nutrition-mcp, covering claude.md, project overview, deploying, publishing to the registry and commands.
projektor AGENTS.md
AGENTS.md instructions for TAJD/projektor, covering agents.md, what projektor is, coordination model (read this first), planning and design docs live in the wiki, not the repo and architecture: the service-layer contract (most important).
Ornn CLAUDE.md
Claude Code instructions for ChronoAIProject/Ornn, covering claude.md — chrono-ornn, product positioning, tech stack, architecture and code standards.
munkel CLAUDE.md
Claude Code instructions for limehq/munkel, covering claude.md, monorepo layout, commands, macos development specifics and deploy.
rewind AGENTS.md
AGENTS.md instructions for pdugan20/rewind, covering rewind, work modes, development commands, agent configuration and architecture overview.