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/josephoibrahim/synapse/agents-mdgit clone --depth 1 https://github.com/JosephOIbrahim/SynapseWhat 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.02660 | $0.02660 |
| Opus 5 | $0.01330 | $0.01330 |
| Sonnet 5 | $0.00532 | $0.00532 |
| Haiku 4.5 | $0.00266 | $0.00266 |
Grade A, and why
Synapse 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 2d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — How agents work on SYNAPSE
Law for every subagent, workflow leg, and orchestrator that touches this repo.
CLAUDE.mdsays what SYNAPSE is. This says how you are allowed to build it. If the two disagree,CLAUDE.mdwins and you file the contradiction.
0 · Prime directive
Produce evidence, not confidence.
Every claim you make must be traceable to something a hostile reader can re-run: a file path with a line number, a probe artifact, a test name, a command and its output. A sentence with no producer path is a rumor.
The single most expensive failure mode in this repo is not a bug. It is a green receipt for work that did not happen. Everything below exists to make that failure structurally hard.
1 · The Seven Laws
Law 1 — Honest seam
A capability whose substrate is not installed reports UNAVAILABLE with the
reason. Never a fabricated SUCCESS. Never a guessed BLOCK. Never a
placeholder that returns the shape of an answer without the answer.
A stub that returns
SUCCESSis worse than no stub. No stub fails loud; a lying stub fails silent and takes a test suite hostage with it.
Law 2 — Absence has a shape
Absence is a measured fact, not a missing feature — and how you degrade depends on which side of the seam the absent substrate sits. See §2.
Law 3 — Runtime is truth
A live-introspected surface beats a doc claim. A probe artifact beats a pinned constant. If the doc and the runtime disagree, the runtime is right and the doc is a bug you now own.
Before emitting any hou.* / pdg.* / pxr.* symbol you are not certain of,
call synapse_scout. Phantom APIs are this repo's #1 historical failure class.
Law 4 — Unmeasured renders UNKNOWN
No estimates. No "should be roughly." An unmeasurable goalpost is written
UNKNOWN and the leg does not go green on it.
Law 5 — Receipts or it did not happen
Every leg posts a receipt to its board's bus/ before it reports done. The
receipt carries: what you touched, the command you ran, the artifact path, the
verdict, and what you could not verify. The last field is not optional, and
"none" is rarely the honest answer.
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.
- 2d ago First seen · 272 lines · 2,660 tokens per session scan A b5a977f9477e
Synapse AGENTS.md is an instructions file published in the GitHub repository JosephOIbrahim/Synapse (10 stars, last pushed 11d ago), licensed MIT. It adds 2,660 tokens to every session, about $0.0133 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
dcc-mcp-houdini GEMINI.md
Instructions for dcc-mcp/dcc-mcp-houdini, covering gemini.md — google gemini / vertex ai integration guide, what this project does, integration setup, gemini-specific tips and quick test prompts.
dcc-mcp-core AGENTS.md
Instructions for dcc-mcp/dcc-mcp-core, covering agents.md — dcc-mcp-core, ⚡ critical: skills-first philosophy, 🚀 agent entry strategy: cli+rest (default) vs ide mcp, response language and command efficiency.
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
open-supermarkets AGENTS.md
Instructions for abracadabra50/open-supermarkets, covering agent integration guide, supported frameworks, quick integration, 1. add as skill and 2. agent calls commands.
helm copilot-instructions.md
Instructions for PetePeter/helm, covering gamepad-cli-hub — copilot instructions, project purpose, system overview, data flow pipeline and key controls.
fusion-skills AGENTS.md
AGENTS.md instructions for CrowdStrike/fusion-skills, covering agents.md, what this is, prerequisites, repository structure and skills ecosystem.