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/holetron-lab/godcrm/agents-mdgit clone --depth 1 https://github.com/Holetron-lab/godcrmWrote 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/holetron-lab/godcrm/agents-md)<a href="https://agentmods.dev/instructions/holetron-lab/godcrm/agents-md"><img src="https://agentmods.dev/badge/instructions/holetron-lab/godcrm/agents-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.00736 | $0.00736 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
godcrm AGENTS.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 4d 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.
This is a copy
84% identical to tabularis AGENTS.md — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus — Code Intelligence
This project is indexed by GitNexus as God_crm (24966 symbols, 53733 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
Index stale? Run
node .gitnexus/run.cjs analyzefrom the project root — it auto-selects an available runner. No.gitnexus/run.cjsyet?npx gitnexus analyze(npm 11 crash →npm i -g gitnexus; #1939).
Always Do
- MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run
impact({target: "symbolName", direction: "upstream"})and report the blast radius (direct callers, affected processes, risk level) to the user. - MUST run
detect_changes()before committing to verify your changes only affect expected symbols and execution flows. For regression review, compare against the default branch:detect_changes({scope: "compare", base_ref: "main"}). - MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
- When exploring unfamiliar code, use
query({search_query: "concept"})to find execution flows instead of grepping. It returns process-grouped results ranked by relevance. - When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use
context({name: "symbolName"}). - For security review,
explain({target: "fileOrSymbol"})lists taint findings (source→sink flows; needsanalyze --pdg).
Never Do
- NEVER edit a function, class, or method without first running
impacton it. - NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
- NEVER rename symbols with find-and-replace — use
renamewhich understands the call graph. - NEVER commit changes without running
detect_changes()to check affected scope.
Resources
| Resource | Use for |
|---|---|
gitnexus://repo/God_crm/context |
Codebase overview, check index freshness |
gitnexus://repo/God_crm/clusters |
All functional areas |
gitnexus://repo/God_crm/processes |
All execution flows |
gitnexus://repo/God_crm/process/{name} |
Step-by-step execution trace |
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.
- 4d ago First seen · 45 lines · 736 tokens per session scan A 6b436ccc3889
godcrm AGENTS.md is an instructions file published in the GitHub repository Holetron-lab/godcrm (0 stars, last pushed today), licensed MIT. It adds 736 tokens to every session, about $0.0037 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to tabularis AGENTS.md, differing in 21 lines, and is treated as a copy.
Other instructions, from other repositories
claude-prompts-mcp CLAUDE.md
Claude Code instructions for minipuft/claude-prompts-mcp, covering claude prompts mcp -- operator handbook, core principles, node.js support boundaries, validation gates (one contract, impact-aware subsets) and fleet standards upstream (minipuft/repository-standards).
claude-prompts-mcp AGENTS.md
AGENTS.md instructions for minipuft/claude-prompts-mcp, covering agent rules · claude prompts mcp, canonical ownership and loading, core principles, node.js support boundaries and validation gates (one contract, impact-aware subsets).
simap-mcp CLAUDE.md
Claude Code instructions for Digilac/simap-mcp, covering claude.md, project overview, documentation, commands and source layout.
pipedrive-mcp-server CLAUDE.md
Instructions for ckalima/pipedrive-mcp-server, covering pipedrive mcp server, commands, architecture, api versions and docs: public vs. private.
ChainWeaver AGENTS.md
Instructions for dgenio/ChainWeaver, covering chainweaver — agent instructions, 1. project identity, 2. domain vocabulary, 3. repository layout and 4. core invariants.
maidan CLAUDE.md
Instructions for david-engelmann/maidan, covering agent guide, 30-second orientation, read order, the cluster model in one paragraph and pr workflow (the short version).