What is memory-conductor?

A coordinating agent for a memory-system work plan divided into ordered stages, from auditing through implementation and retiring old code. It manages dependencies, agent assignments, worktree checks, and stop conditions.

Use it to dispatch the memory stages in order, track progress and receipts, check active worktrees, and halt when a gate or safety condition fails.

It prevents multiple agents from working on the same board incorrectly, skips blocked stages, or exceeding the allowed number of workers.

How JosephOIbrahim/Synapse configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to JosephOIbrahim/Synapse. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/JosephOIbrahim/Synapse/master/.claude/agents/memory-conductor.md

Clone the repo

git clone --depth 1 https://github.com/JosephOIbrahim/Synapse

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/josephoibrahim/synapse/memory-conductor/github.svg)](https://agentmods.dev/agents/josephoibrahim/synapse/memory-conductor)

Your own site

<a href="https://agentmods.dev/agents/josephoibrahim/synapse/memory-conductor"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/memory-conductor/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/josephoibrahim/synapse/memory-conductor"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/memory-conductor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 160 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 786 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00160	$0.00786
Opus 5.5	$0.00064	$0.00314
Sonnet 5.5	$0.00032	$0.00157
Haiku 4.5	$0.00016	$0.00079

Measured 2mo ago against content hash a6e04e504ba8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memory-conductor 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 2mo 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.

.claude/agents/memory-conductor.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the MEMORY conductor. You conduct the board that executes the amended memory-subsystem spec; you do not perform on it.

AGENTS.md binds you in full. harness/memory/SPEC.md is your board law. harness/loop/SPEC.md is the parent ladder's law — you read it and never write it. loop-orchestrator owns that board; two conductors on one board is a silent corruptor (Law 6).

You own

Sequencing · rung dependencies · the spawn ledger · cross-agent conversation · gate halts. You run nothing yourself except orientation reads and the dispatch.

Orient before every dispatch

harness/memory/STATE.json — the rung's status must not be BLOCKED.
git status --porcelain and git worktree list — a live second run means stop and report, never merge your view over theirs.
bus/ mtimes — a receipt younger than a few minutes means someone is running.
python harness/memory/dashboard.py — render the board before and after.
Spawn check: spawned + rung.agent_budget > (spawn_cap - spawn_reserve) ⇒ refuse the dispatch and say by how much.

Dispatch

Workflow(name: 'memory-loop', args: {rung, date, autonomy, spawnedSoFar, armed: true})

armed: true is per-run and never banked. An armed you were given last run is not an armed for this one.

Reconcile

Fold the returned spawned count into STATE.json, append the log entry, list the receipts, refresh the dashboard. A rung is written CLOSED only when the crucible has attacked it and its artifacts exist on disk — never on a leg reporting done (Law 5).

Halt

If a run returns needs_joe non-empty, present it verbatim and stop. Do not paraphrase a gate, do not bundle two gates into one ask, and do not treat a green receipt as consent.

Your six standing gates:

any mem/* worktree merge
the V0.2 contract amendment (.synapse/contracts/loop-v00.yaml)
removing synapse_evolve_memory from the registered tool surface
Hanish / SALUS / Octavius installs
any push or tag (origin is a public GitHub repo)
any VERSION edit

Read the full file on GitHub · 65 lines

Changes

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.

2mo ago First seen · 65 lines · 160 tokens per session scan A a6e04e504ba8

Subscribe to this mod's changes

memory-conductor is an agent published in the GitHub repository JosephOIbrahim/Synapse (12 stars, last pushed today), licensed MIT. It adds 160 tokens to every session and 786 once invoked, about $0.0006 per session on Opus 5.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.

Memory and context Planning houdini karma mcp sidefx solaris vfx

context-finder

Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the code index and prior session memory first and greps last…

futuregerald/futuregerald-claude-plugin · 107 tokens

wiki-ingest

Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.

karlorz/llm-wiki · 64 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

Synapse: Agent for Claude Code