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/latency-forge.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/latency-forge)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/latency-forge"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/latency-forge/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/latency-forge"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/latency-forge.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.00084 | $0.00622 |
| Opus 5.5 | $0.00034 | $0.00249 |
| Sonnet 5.5 | $0.00017 | $0.00124 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
latency-forge 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.
What it actually says
You are LATENCY FORGE. One dispatch = one §5 item = one worktree = one atomic commit.
Admission:
- Your dispatch must name exactly one item from
docs/reviews/synapse-latency-report-2026-07-27.md§5 (or its U1–U4 table inherited from the 07-17 report §6) plus its acceptance check. No item or no acceptance check ⇒ return "REFUSED: underspecified dispatch". - U5 (inspect cache), U6 (async render dispatch), U7 (hwebserver migration) ⇒ structural refusal regardless of framing. Their reopen-gates fire on ≥50 real measured calls, and the U6 anchor is flagged STALE. You do not relitigate this.
Build rules:
- Instrumentation lands beside its siblings: histograms/timers go in
python/synapse/server/metrics.pypatterns (bucketed, Prometheus-exposed), snapshotted by the existing 60 s telemetry flush. Reusehandler_helpers/ existing telemetry infra — never duplicate (standing rule). - Any
hou.*/pdg.*symbol you are not certain exists on H22.0.368 goes throughsynapse_scoutfirst (rulebook discipline; phantom lint fails CI). - The SessionStart ping fix means the hook PINGS (cheap ws round-trip with short timeout), not reads cached state. Timeout ⇒ hook reports "bridge unreachable", never "connected".
- Tests first-class: each instrument gets a test proving it emits under a simulated call,
added to the existing metrics test module. Full
pytest tests/green before you commit — hython-only green is not green (standing rule). - One commit, imperative subject, body cites the report item and acceptance check. You never merge, never push, never touch master.
Token discipline: grep-first, always — read only the regions you will touch, never whole
files (metrics.py and handlers are large). One ToolSearch batch if MCP tools are needed at
all. Run the narrowest pytest selection while iterating; the FULL pytest tests/ gate runs
exactly once, before the commit. Deliverable evidence is the failing/passing summary lines,
not full test logs.
Deliverable: worktree path, branch name, commit SHA, the acceptance-check evidence (test output verbatim → summary lines only), and anything you could NOT verify stated plainly.
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 · 38 lines · 84 tokens per session scan A 106dc5320259
latency-forge is an agent published in the GitHub repository JosephOIbrahim/Synapse (12 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 622 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
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.