Borrowing it
Nothing to install: this file belongs to khaoss85/agent-crm. 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/khaoss85/agent-crm/main/CLAUDE.mdgit clone --depth 1 https://github.com/khaoss85/agent-crmWrote 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/khaoss85/agent-crm/claude-md)<a href="https://agentmods.dev/instructions/khaoss85/agent-crm/claude-md"><img src="https://agentmods.dev/badge/instructions/khaoss85/agent-crm/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.01146 | $0.01146 |
| Opus 5 | $0.00573 | $0.00573 |
| Sonnet 5 | $0.00229 | $0.00229 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
agent-crm 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 6d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code guidance
Read AGENTS.md first and follow it as the canonical repository guidance.
Before substantial work, also read PRODUCT.md, ARCHITECTURE.md, DECISIONS.md and the relevant skill under .claude/skills/.
Selecting an Accordo rail
The application answers questions about itself through a small set of rails —
few tools, distinct jobs. When one of the questions below is the question in
front of you, run its rail rather than assembling the answer from find,
grep and source reading: hand-assembly is slower, and it tends to fail by
inventing a capability the application does not have
(docs/APPLICATION_INSPECTION.md).
| The question in front of you | Rail | Command |
|---|---|---|
| What has this project actually composed? | SEE | npm run crm -- app inspect --json |
| Is this plan valid, and still true of this application? | PLAN | npm run crm -- solution check <plan.json> |
| What is inconsistent or stale in this checkout? | CHECK | npm run crm -- project doctor --json |
| I need a minimal new package starting point. | BUILD | npm run crm -- package scaffold <name> |
| Does this one package conform to the framework? | CHECK | npm run crm -- package test <dir> --json |
| Is the whole project technically healthy? | PROVE | npm run crm -- project verify --json |
| Does this business journey actually work? | PROVE | npm run crm -- scenario run <scenario> --json |
| Is every requirement of the plan actually proven? | PROVE | npm run crm -- solution verify <plan.json> --evidence <evidence.json> |
| Will this refactor preserve behaviour? | PRESERVE | characterization — tests/characterization/, npm run characterize:intelligence |
The selection rule. Use the smallest rail that directly answers the current
question. Do not chain rails automatically, and no rail — app inspect
included — is an obligatory first step. Escalate only when the next question
needs a stronger kind of evidence: what exists → inspect · internally
consistent → doctor · technical health proven → project verify · this journey
proven → scenario run · the plan proven complete → solution verify.
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.
- 6d ago First seen · 78 lines · 1,146 tokens per session scan A aa9271adff03
agent-crm CLAUDE.md is an instructions file published in the GitHub repository khaoss85/agent-crm (2 stars, last pushed 4d ago), licensed MIT. It adds 1,146 tokens to every session, about $0.0057 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.