Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sohilladhani/codesynapsenpx agentmods add rules/sohilladhani/codesynapse/codesynapse-cliWrote 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/rules/sohilladhani/codesynapse/codesynapse-cli)<a href="https://agentmods.dev/rules/sohilladhani/codesynapse/codesynapse-cli"><img src="https://agentmods.dev/badge/rules/sohilladhani/codesynapse/codesynapse-cli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/sohilladhani/codesynapse/codesynapse-cli"><img src="https://agentmods.dev/badge/rules/sohilladhani/codesynapse/codesynapse-cli.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01032 |
| Opus 5.5 | $0.00000 | $0.00413 |
| Sonnet 5.5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
codesynapse-cli 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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codesynapse CLI
Codesynapse has pre-indexed this codebase into a knowledge graph that knows about classes, functions, their relationships (calls, extends, implements), and source locations. The graph is more precise than grep for architecture questions.
MCP may not be available. All codesynapse commands run via bash terminal (Cmd+J / Ctrl+J). Use the codesynapse binary — if not found, try /usr/local/bin/codesynapse then ~/.local/bin/codesynapse (the two standard install locations). The project graph is at ./codesynapse-out/graph.json. Run codesynapse module list to see all indexed modules.
Use codesynapse CLI commands before grep/find for architecture questions.
Quick Reference
| Intent | Command |
|---|---|
| General codebase query | codesynapse query "<question>" --graph <path> |
| Node details + relationships | codesynapse explain <id> --path <graph-path> |
| Shortest path A → B | codesynapse path <A> <B> |
| Blast radius of X | codesynapse affected <X> --graph <path> --depth 2 |
| Graph statistics | codesynapse stats <path> |
| God/central nodes | codesynapse analyze <path> |
| Community detection | codesynapse cluster <path> |
| Module list | codesynapse module list |
| Graph diff | codesynapse diff <path> --baseline <other> |
Decision Tree
STEP 1 — Architecture questions ("how does X work", "what handles Y", "where is Z defined"):
codesynapse query "<question>" --graph ./codesynapse-out/graph.json
STEP 2 — Need details on a specific node:
codesynapse explain <ClassName> --path ./codesynapse-out/graph.json
STEP 3 — Blast radius / change impact:
codesynapse affected <ClassName> --graph ./codesynapse-out/graph.json --depth 2
STEP 4 — Dependency tracing / request flow:
codesynapse path <FromClass> <ToClass>
STEP 5 — Module ownership:
codesynapse query "<concept>" --graph ./codesynapse-out/graph.json
# Check file paths in results
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.
- 1mo ago First seen · 100 lines · 0 tokens per session scan A e3057cf06e0e
codesynapse-cli is a cursor rule published in the GitHub repository sohilladhani/codesynapse (8 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,032 tokens. 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 cursor rules, from other repositories
roslyn-mcp-pitfalls
Known pitfalls and regression lessons from production use.
roslyn-mcp-decompile
Assembly resolve, ILSpy decompile, NuGet/BCL fallback.
roslyn-mcp-paths
Path resolution, searchcode defaults, workspace-relative paths.
code-style
Formatting, lint, comments language.
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
roslyn-mcp-docs-agents
Docs sync AGENTS/README, agent conventions, PowerShell, secrets.