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/redberryproducts/synapse/agents-mdgit clone --depth 1 https://github.com/RedberryProducts/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.05050 | $0.05050 |
| Opus 5 | $0.02525 | $0.02525 |
| Sonnet 5 | $0.01010 | $0.01010 |
| Haiku 4.5 | $0.00505 | $0.00505 |
Grade B, and why
synapse AGENTS.md scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -sN -o /dev/null -X POST http://127.0.0.1:8000/synapse/api/chat/app.agents.slow-tool-agent/send -b cookies.txt -H "X-XSRF-TOKEN: $TOKEN" -H 'Content-Type: application/json' -d '{"message":"Query the analytics servic Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sN -o /dev/null -X POST http://127.0.0.1:8000/synapse/api/chat/app.agents.slow-tool-agent/send -b cookies.txt -H "X-XSRF-TOKEN: $TOKEN" -H 'Content-Type: application/json' -d '{"message":"Query the analytics servic How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on Synapse
Guidance for any agent or contributor writing code in this repository. Read this first, then DEV.md for exact commands. For how Laravel packages work, invoke the laravel-package skill. For what we're building, GOAL.md (user-facing) and PRD.md (technical) are the source of truth.
Important notes
- Plan before coding. For a non-trivial task, state a short plan (steps → how you'll verify each) and work through it.
- Run the gates before reporting done:
composer check(lint + analyse + test). All green, every time. A pre-commit hook enforces this — enable it once withcomposer hooks. - Run
composer test:e2ewhen you touch the frontend or the chat/stream surface. It's excluded fromcomposer checkand from CI (needs Playwright + built assets); it is a required gate before a release. - Rebuild
dist/(npm run build) wheneverresources/jschanges — it's committed, and the hook checks it. - Never
git commitwithout being asked. - PRD.md / GOAL.md are the spec. If code and spec disagree, stop and reconcile — don't invent behavior.
What this is
Synapse (redberry/synapse, namespace Redberry\Synapse\) is a Laravel package: a development dashboard for AI agents built with the Laravel AI SDK (laravel/ai). A React SPA served by a Laravel service provider — think Telescope/Horizon, but for AI agents. The scaffold is complete and green (Pest, Pint, PHPStan); feature work builds on top of it.
Repository map
src/ # PHP — the package
├── SynapseServiceProvider.php # register/boot: routes, views, publish, commands, schedule
├── SynapseApplicationServiceProvider.php # base for the published gate provider
├── Synapse.php # static helpers: asset tags, script vars, auth callback
├── Http/{Controllers,Middleware}/ # HomeController (SPA shell), Authorize (viewSynapse gate)
├── Console/ # Install / Prune / Clear commands
├── Migrations/SynapseMigration.php # legacy migration base retained for compatibility
├── Models/ # SynapseModel base + Conversation/Message/ToolInvocation
└── Repositories/ # ConversationRepository (cascade delete lives here)
config/synapse.php # publishable config (enabled, ui, discovery, playground, storage, retention)
database/migrations/ # three self-contained synapse_* tables (publish-only)
routes/web.php # /api group (stubbed) + SPA catch-all
resources/js/ # React + TS SPA — elements/ → components/ → composed/ → pages/
# (+ hooks, lib, types, styles)
resources/views/layout.blade.php # SPA shell + window.Synapse bootstrap
stubs/ # SynapseServiceProvider.stub (published viewSynapse gate)
dist/ # compiled assets — COMMITTED, published on install
workbench/ # Testbench dev app + 4 sample agents
tests/ # Pest + Testbench (Unit/, Feature/, Browser/ e2e)
.githooks/ # pre-commit hook (enable with `composer hooks`)
testing-laravel-project/ # gitignored real app for manual install testing (bin/setup-testing-app.sh)
references/ # gitignored: laravel/ai, telescope, horizon (read-only reference)
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 · 284 lines · 5,050 tokens per session scan B 652d955014e8
synapse AGENTS.md is an instructions file published in the GitHub repository RedberryProducts/synapse (22 stars, last pushed 5d ago), licensed MIT. It adds 5,050 tokens to every session, about $0.0252 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.