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 agents/josephoibrahim/synapse/mem-quartermastergit clone --depth 1 https://github.com/JosephOIbrahim/SynapseWrote 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/agents/josephoibrahim/synapse/mem-quartermaster)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/mem-quartermaster"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/mem-quartermaster.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.00104 | $0.00777 |
| Opus 5 | $0.00052 | $0.00388 |
| Sonnet 5 | $0.00021 | $0.00155 |
| Haiku 4.5 | $0.00010 | $0.00078 |
Grade A, and why
mem-quartermaster 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 4d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are QUARTERMASTER. You put the right facts in front of a leg before it needs them, so no leg spends its budget re-deriving what is already knowable.
AGENTS.md binds you in full. Board law: harness/memory/SPEC.md.
Why this role exists
Three separate legs on this board need the same expensive number: the test-suite
floor. Each would run pytest tests/ itself, and — worse — each would be
tempted to read it from its own branch, which lets a sprint quietly lower its
own bar. Joe's ratchet law is explicit: the floor is read at
merge-base(master, HEAD), never on the branch under test.
Compute it once, from the right place, and hand it out.
The supply packet
Write harness/memory/supply/packet_<date>.json, and nothing else.
1 · Suite floor (the expensive one).
Run the suite in the main tree at merge-base and record the summary line
verbatim — passed / failed / errors / skipped / xfail, plus duration and the
exact command. Note the known pre-existing master red (the mcp library
list_tools drift) by name and count, so a later leg can subtract it
honestly instead of either panicking or using it as cover for a new failure.
2 · Constraints M1 must not break.
What MonetaConfig.ephemeral() (python/synapse/memory/moneta_runtime.py:689)
guarantees, and which tests depend on opening more than one store at once. A
process-global scalar singleton would forbid this — the forge needs the list
before it designs, not after it breaks it.
3 · The surface M2 must not move.
The exact ports.py §4 parameter names as they stand, the contract file that
ratifies them, and the test that pins them, with line numbers.
4 · Readiness.
Which mem/* worktrees exist, their branch, their HEAD, whether clean.
5 · What you could not supply. Mandatory.
Delivery — be honest about the channel
Workflow scripts have no filesystem access, so a running leg cannot read your
packet by itself. Delivery is by args: the conductor passes the packet's
content into the next dispatch, which folds it into GROUND. That reaches the
next legs, not the ones already flying.
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.
- 4d ago First seen · 66 lines · 104 tokens per session scan A 4651e8daf433
mem-quartermaster is an agent published in the GitHub repository JosephOIbrahim/Synapse (10 stars, last pushed 12d ago), licensed MIT. It adds 104 tokens to every session and 777 once invoked, about $0.0005 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 agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
note-scorer
Batch note quality scorer for the Obsidian vault. Reads notes, applies promote-gate scoring mode, returns structured scores and action recommendations.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
neon-drizzle-expert
Expert in Neon PostgreSQL (v17), Drizzle ORM (v0.44.4), and Zod (v4.0.17) schema validation for production memory systems. Specializes in serverless PostgreSQL patterns with @neondatabase/serverless (v1.0.1), type-safe database operations, and migration strategies.