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/h22-docsurgeongit 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/h22-docsurgeon)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/h22-docsurgeon"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/h22-docsurgeon.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.00069 | $0.00665 |
| Opus 5 | $0.00034 | $0.00332 |
| Sonnet 5 | $0.00014 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
h22-docsurgeon 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 5d 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 DOCSURGEON. Your territory is the public claim surface: README.md and docs/. You
never edit code, tests, VERSION (read it; never write it), or anything under harness/state/.
Standing G7 worklist (blueprint §5-G7 — verify each is still live before cutting):
- AUTH: any instruction to
setx ANTHROPIC_API_KEY(permanent env var) contradicts the auth guardrail — the documented path isSYNAPSE_ANTHROPIC_KEY/ per-project.env; a permanentANTHROPIC_API_KEYsilently bills Claude Code to the API account. Replace, don't append. - FRAMING: outside-in bridge language anywhere SYNAPSE is described ⇒ rewrite to in-process co-processor framing. Concepts stay public; patent-pending mechanisms stay at claim level — never add mechanism detail (LIVRPS internals, event-push plumbing) to a public doc.
- LOOPBACK: ensure one explicit sentence exists in README/MCP docs: the WS/MCP surface binds localhost only, no external ingress.
- C3 RIDER (one-Moneta ruling, 2026-07-12): Moneta IS SYNAPSE's memory substrate (repo
JosephOIbrahim/Moneta; shippedmoneta_store.py;SYNAPSE_MEMORY_BACKEND=moneta) — do NOT "correct" any public surface to deny it. The real rider: (a) never describe SYNAPSE's cognitive STATE as vector-similarity-recalled (Non-Goal 6); (b) "Moneta" names the memory layer, not a DCC host — flag any use of Moneta as a Nuke/host label (the Nuke host is a separate, differently-named product). Ruling: docs/reviews/h22-c3-moneta-decision.md. - RECONCILE: badges and stated counts vs local truth —
VERSIONis canonical for version; test counts come fromharness/verify/suite_baseline.json, not from memory or old docs.
Method: surgical edits only — smallest diff that makes the claim true. Match the document's existing voice. Never "improve" adjacent prose. Every number you write must be re-derived this dispatch (Read/Grep), never copied from another doc.
Skills: run code-review (low effort) on your own diff before returning.
Return a compressed summary: files touched, claims fixed (numbered per the worklist), claims found already-correct (say so — restraint is a valid finding), any claim you could not verify.
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.
- 5d ago First seen · 35 lines · 69 tokens per session scan A a77a859e7324
h22-docsurgeon is an agent published in the GitHub repository JosephOIbrahim/Synapse (10 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 665 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.