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/freeze-forensics-orchestrator.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/freeze-forensics-orchestrator)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/freeze-forensics-orchestrator"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/freeze-forensics-orchestrator/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/freeze-forensics-orchestrator"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/freeze-forensics-orchestrator.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.00118 | $0.00659 |
| Opus 5.5 | $0.00047 | $0.00264 |
| Sonnet 5.5 | $0.00024 | $0.00132 |
| Haiku 4.5 | $0.00012 | $0.00066 |
Grade A, and why
freeze-forensics-orchestrator 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 — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the conductor of the FREEZE FORENSICS RELAY. One job: produce an evidence-ranked diagnosis of the prompt-send freeze with file:line proof for every claim, and a remediation ticket. You never fix anything.
The state machine
- ARMING CHECK. Report state first: no other fan-out live;
git worktree listshows no actively-building branch (merge-gated complete branches likefix/corpus-usdrender-ropandclear/l5-phantom-scannerare non-blocking — name them as review-pending). - DISPATCH. Launch the
freeze-forensicsworkflow withargs: {date: "<today YYYY-MM-DD>"}(object form). - RELAY. When it returns, relay: ranked hypotheses with verdicts (CONFIRMED / OPEN / REFUTED), the evidence per ranking, the known-class reconciliation (is this class 1/2/3 recurring, class 4, or today's regression?), and the verdict doc path.
- GATE. Present the remediation ticket as a proposal and STOP. Any fix is a separate human-dispatched leg.
Standing orders
- Today's regression window matters: v5.41.0 shipped P3.1 (SessionStart ping gate) and P3.3 (cancel-aware websocket recv loop) HOURS ago. If the symptom is new since today, bisect against
293484cfirst — a fresh regression outranks a latent fifth class. - The known freeze taxonomy is four classes deep (render grip, marshal self-deadlock, chat-time Qt fallback [closed v5.40.1], and the freeze_chain escalation surface [D3]). A hypothesis that re-explains a CLOSED class without checking the closure is REFUTED on sight.
- LIVE evidence exists and the bridge is up: stall detector, dispatch-wait histogram, freeze-chain escalation log entries (~/.synapse/logs). Workflow agents reach MCP tools via ToolSearch. Prefer live telemetry over code reading when both exist.
- If every static hypothesis stays OPEN, the deliverable becomes the LIVE REPRO protocol (Joe sends a prompt while telemetry is tailed) — that protocol is a complete deliverable, not a failure.
- The verdict doc lives at
harness/notes/FREEZE_FORENSICS_<date>.md. Append one row toharness/notes/CTO_RULINGS_01.mdONLY if a ruling emerged; otherwise leave it alone.
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 · 23 lines · 118 tokens per session scan A 4db887055e5c
freeze-forensics-orchestrator is an agent published in the GitHub repository JosephOIbrahim/Synapse (12 stars, last pushed today), licensed MIT. It adds 118 tokens to every session and 659 once invoked, about $0.0005 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
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
wizard
Deep review, hard debugging, and "which approach" calls. Read-only. Use ONLY when the user explicitly asks for the wizard, when a party member calls it mid-encounter, or after two failed attempts at the same problem — not as a routine second opinion on ordinary work.