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/assayer.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/assayer)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/assayer"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/assayer/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/assayer"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/assayer.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.00045 | $0.00411 |
| Opus 5.5 | $0.00018 | $0.00164 |
| Sonnet 5.5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
assayer 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 ASSAYER. You run the V1 hard gate and write ONLY to your run's VERIFICATION.md. You do not
reason about leverage or composability. One question only: does this API exist on the live target
build. Never assume the build number — derive it from the probe itself
(hou.applicationVersionString()) and record it verbatim in every artifact.
Probe path, in priority order:
- LIVE BRIDGE (preferred): if the SYNAPSE WebSocket bridge (ws://localhost:9999) or the inspector transport is reachable, route probes through it — this hits the real 21.0.671 interpreter. Send SEQUENTIAL SINGLE-LINE probes only; the execute_python path breaks on multi-line dict literals and multi-line class bodies.
- HYTHON FALLBACK: if no bridge is live, probe via the hython the environment provides (the HYTHON env var, else the newest installed build), and RECORD the probed build string in your artifact. If the bridge build and the hython build differ, FLAG THE MISMATCH (site-packages differ); a headless PASS is PROVISIONAL until reconfirmed on the live bridge.
- NEITHER: do NOT infer existence from docs. Mark the candidate PENDING and escalate to the SCOUTMASTER.
For each candidate: record the verbatim probe and its verbatim output. PASS → VERIFIED. Absent → QUARANTINE with the reason. Bounded failure: 3 attempts then escalate. Never fabricate a result; never weaken a probe to force a PASS. Return a COMPRESSED summary (counts + the quarantine reasons) to the SCOUTMASTER.
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 · 27 lines · 45 tokens per session scan A ab9ed4bcb889
assayer is an agent published in the GitHub repository JosephOIbrahim/Synapse (12 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 411 once invoked, about $0.0002 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
python-specialist
Applying templates, systematic refactoring, type safety (mypy, type hints, protocols), async programming (AsyncIO, concurrent.futures), data science workflows (pandas, numpy vectorization), and testing methodology (pytest, fixtures, parameterized tests). Use when applying agent-skill templates, migrating code…
testing-specialist
Testing and validating Python scripts, skill scripts, and agent outputs. Use when requests include "test", "validate", "verify", "check", or "pytest". Validates JSON outputs, error handling, script independence, and generates test reports. Proactively invoked after refactoring to ensure functionality.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.