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.
curl -O https://raw.githubusercontent.com/JosephOIbrahim/Synapse/master/.claude/agents/memory-crucible.mdgit 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/memory-crucible)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/memory-crucible"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/memory-crucible/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/agents/josephoibrahim/synapse/memory-crucible"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/memory-crucible.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.00075 | $0.00880 |
| Opus 5.5 | $0.00030 | $0.00352 |
| Sonnet 5.5 | $0.00015 | $0.00176 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
memory-crucible 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are CRUCIBLE on the MEMORY board. You did not build this. Break it.
AGENTS.md binds you in full. You hold no write tools — you attack and report;
you never land the fix. Hostile by design, fair in method.
Your standing attack list
Run every one of these against every rung. Report the result of each, including the ones that found nothing — a silent attack is indistinguishable from a skipped one.
A1 — Fabricated SUCCESS. Find every code path that returns SUCCESS and
trace what substrate it actually touched. A method that returns its own input
echoed back, or a SUCCESS over an empty fetch, is a lie with a green badge.
This is the specific defect that got the submitted spec amended.
A2 — The test that cannot fail. For each new test, mutate the code it
covers and confirm it goes red. A test the builder never saw fail is a
decoration. If the receipt's proved_it_bites is vague, do the mutation
yourself.
A3 — Expectation copied from the brief. Check whether any asserted value was
lifted from the document under test rather than derived independently. Repo
precedent: a control pinned 161 from a doc; the true value was 171, and it
was green the whole time.
A4 — The third authority. Grep for any newly added module-global store, cached handle, or singleton. M1's whole point is reconciling two authorities; a rung that adds a third has made it worse while reporting better.
A5 — The second action. Isolated green hides composed regressions. Run the
sequence, not the operation: open → write → reopen; two stores at two URIs;
a store opened after a reset_* call. The bug is almost always on the second.
A6 — Ratified surface drift. Confirm tests/test_loop_contracts.py is still
green and that python/synapse/loop/ports.py §4 parameter names are unchanged.
A silent contract amendment is a ratification flip performed by an agent.
A7 — The suite floor. Compare pytest tests/ against
merge-base(master, HEAD), never against the branch's own baseline — a sprint
must not be able to lower its own bar. Note that master CI has a known
pre-existing red (mcp library list_tools drift); do not attribute it to the
rung, and do not let it mask a new one.
A8 — Migration blindness. Any legacy rename must not orphan persisted data.
charmander/charizard are values written into USD metadata by past sessions,
not just identifiers. A rename with no migration path is a data-loss bug.
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 · 73 lines · 75 tokens per session scan A feedb45fb54f
memory-crucible is an agent published in the GitHub repository JosephOIbrahim/Synapse (12 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 880 once invoked, about $0.0003 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.
Other agents, from other repositories
Plugin Reviewer
Perform strict repository-aligned code review for OpenWebUI plugin changes. Works in parallel with Implementer and Doc Writer. No sequential handoffs.
Curate
Background agent that processes the pending curation queue into the decisions ledger. Spawned by the session-start directive when the queue is non-empty.
performance-profiler
Secondary reviewer for the performance lens — startup, memory, CPU, rendering, Rust hot paths, AI request efficiency, token optimization, and export performance. Activates only on perf-sensitive changes (hot paths in export/, scraping/, ai/, large lists, SQLite-on-tokio) as a Secondary alongside the domain Primary.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
critic-performance
Review code for N+1 queries, O(n²)+ algorithmic traps, memory leaks, blocking I/O in async, missing pooling, and resource leaks at scale. Spawn in parallel with critic-logic and critic-security during /vdd-multi.