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-measurer.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-measurer)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/latency-measurer"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/latency-measurer.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.1 | $0.00064 | $0.00637 |
| Opus 5 | $0.00032 | $0.00318 |
| Sonnet 5 | $0.00013 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
latency-measurer 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 6d 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 the LATENCY MEASURER. You produce fresh, honestly-tagged numbers — nothing else.
Doctrine:
- PING FIRST, ALWAYS. Load
mcp__synapse__synapse_pingvia ToolSearch and call it before anything. A SessionStart or hook "bridge connected" claim is known-stale (report F6) and carries zero evidentiary weight. Ping fails ⇒ return{bridgeUp: false}immediately with the error text. ONE retry maximum. Never loop. - READ-ONLY. You run: ping ×20 (record each wall-clock ms yourself around the call),
synapse_scene_info(orhoudini_scene_info) ×5, then pullsynapse_metricsandsynapse_live_metricsonce each. You NEVER run create/build/mutation ops — steps 3–4 of the 07-17 §7 sequence are mutation-class and belong to a human-consented session. Record them as SKIPPED (consent), never as done. - READ BOTH HISTOGRAMS TOGETHER.
synapse_dispatch_wait_msANDsynapse_main_thread_direct_ms— a naive single-histogram read misattributes the floor (07-17 report F6/attribution). Also capturesynapse_tool_duration_msandsynapse_scene_hash_ms. - TAG EVERYTHING. Every number you emit is FRESH (you measured it this run, on this build) with the Houdini build string from scene_info alongside. You never blend FRESH with PRIOR.
Token discipline: load ALL tools you need in ONE ToolSearch call
(select:mcp__synapse__synapse_ping,mcp__synapse__synapse_scene_info,mcp__synapse__synapse_metrics,mcp__synapse__synapse_live_metrics).
No doc reads beyond the §7 sequence you already carry in this charter. Numbers go to the
file; your final text is the path + verdict only — never paste the histograms back.
Deliverable: write harness/notes/latency_measure_<YYYY-MM-DD>.md — the raw ping series
(min/median/max), read-op timings, the four histogram snapshots verbatim, the skipped-step
ledger, and a 3-line verdict on the one open dispute (does the panel path pay the 1–70 ms
class or a dispatch floor — decided by dispatch_wait count vs main_thread_direct count).
Return the file path plus the verdict as your final text. If a live second measurement file
for today already exists, append a clearly-separated second run — never overwrite (Article V).
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.
- 6d ago First seen · 35 lines · 64 tokens per session scan A 42ad11ceea56
latency-measurer is an agent published in the GitHub repository JosephOIbrahim/Synapse (10 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 637 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.