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/sohilladhani/codesynapse/claude-mdgit clone --depth 1 https://github.com/sohilladhani/codesynapseWrote 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/sohilladhani/codesynapse/claude-md)<a href="https://agentmods.dev/instructions/sohilladhani/codesynapse/claude-md"><img src="https://agentmods.dev/badge/instructions/sohilladhani/codesynapse/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.00224 | $0.00224 |
| Opus 5 | $0.00112 | $0.00112 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
codesynapse 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.
What it actually says
Codesynapse — Code Intelligence
Tool selection and usage instructions are delivered via MCP initialize — no duplication needed here.
Displaying codesynapse_stats
When the user calls codesynapse_stats, ALWAYS display the tool result verbatim in a code fence:
[paste the entire codesynapse_stats output here]
The output contains Unicode box-drawing characters (╔═╗║╠╣╚╝├┤│) and bar charts (█░) that must be preserved exactly as returned. Do NOT paraphrase or summarize the dashboard — users need to see the visual formatting.
Codesynapse — Code Intelligence
Use these CLI commands to answer architecture questions (works in subagents without MCP):
codesynapse resolve "how does X work"— hybrid search + source bodycodesynapse query "concept name"— find relevant symbols
Repository indexed as module tokio. Re-index: codesynapse module add --force tokio <path>.
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 · 24 lines · 224 tokens per session scan A e3abafc57bcd
codesynapse CLAUDE.md is an instructions file published in the GitHub repository sohilladhani/codesynapse (8 stars, last pushed 1mo ago), licensed MIT. It adds 224 tokens to every session, about $0.0011 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
Ctxo CLAUDE.md
Instructions for alperhankendi/Ctxo, covering claude.md — ctxo, project overview, quick reference, dev (pnpm workspace) and usage (consumer).
sverklo CLAUDE.md
Instructions for sverklo/sverklo, covering sverklo development, using sverklo tools, project structure and build & test.
FsLangMCP CLAUDE.md
Instructions for Neftedollar/FsLangMCP, covering fslangmcp — business workspace, how to start (required for every session), 1. determine mode, 2. load context (depends on mode) and 3. act.
Ctxo copilot-instructions.md
Instructions for alperhankendi/Ctxo, covering ctxo mcp tool usage (mandatory), before any code modification, before starting a task, before reviewing a pr or diff and when exploring or searching code.
agentmako AGENTS.md
Instructions for drhalto/agentmako, covering mako mcp usage, operating model, default workflow, fast batches and freshness.
cortex-hub CLAUDE.md
Instructions for lktiep/cortex-hub, covering cortex hub — claude code instructions, quick start (mandatory), tech stack, code conventions and how to use cortex tools.