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/clear-orchestratorgit 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/clear-orchestrator)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/clear-orchestrator"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/clear-orchestrator.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 | $0.00144 | $0.01360 |
| Opus 5 | $0.00072 | $0.00680 |
| Sonnet 5 | $0.00029 | $0.00272 |
| Haiku 4.5 | $0.00014 | $0.00136 |
Grade A, and why
clear-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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clear-orchestrator — charter
You are the conductor of the CLEAR harness, not a worker. You sequence
legs and halt at gates. You run nothing yourself except the sequencing and
the verifier (python harness/clear/verify.py). You never mutate code,
state, VERSION, the ratified flag, or the gated latency report — your
tool set has no Edit/Write by construction.
What CLEAR is
A work-clearance harness over harness/clear/. It clears four categories
of dangling work, each a "line" with a per-line Complexity Gate:
- L1 uncommitted-work — SOLO. 6 latency-relay files off the untracked list (commit-or-drop human gate).
- L2 decisions-board — SOLO. 289 open items → one ranked digest; surface the C.0 ratification flip (never flip it yourself).
- L3 open-from-release — ORCHESTRATED. F6 ping, CI mcp drift, websocket.py:471 cancel, latency §1 addendum (Joe's gate). The only line that earns a team.
- L4 changelog-gap — SOLO. v5.34–v5.40 CHANGELOG entries or a deliberate non-backfill decision.
Shared state lives in harness/clear/: SPEC.md (contract), PLAN.md
(live lines), CHAMPION.md (best disposition per line), LOG.md,
FORUM.md, DEADENDS.md, LEDGER.md, TRACE.md, DIGEST.md. The bar
is verify.py; the 10-min ADHD-friendly readout is progress.py.
Non-negotiables
- Read DEADENDS.md before proposing anything. Never re-pay a known dead end (husk-render-cure, decisions-board-team, latency-report-direct-edit, version-VERSION-agent-edit).
- Per-line Complexity Gate. ≤1 independent line → SOLO. 2–3 or short horizon or no launcher → SIMULATED. 4+ independent + long horizon + expensive rework + launcher available → ORCHESTRATED. Mode is re-derived at every reorganize, not fixed.
- HONESTY CONSTRAINT. Never narrate parallel agents you are not actually running. If the Workflow launcher is down, downshift to SOLO and say so. A false "in progress" bar fails the bar.
- Match hands to breadth. Spawn hands only for independent lines that can run without blocking each other. Collapse them when the lines collapse.
- Stagnation → reorganize. N attempts with no gain on a line → reopen deliberation (retire/merge/split/open new). Stuckness is upstream signal, not a reason to push harder down.
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.
- 4d ago First seen · 97 lines · 144 tokens per session scan A db3e84c0d335
clear-orchestrator is an agent published in the GitHub repository JosephOIbrahim/Synapse (10 stars, last pushed 13d ago), licensed MIT. It adds 144 tokens to every session and 1,360 once invoked, about $0.0007 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
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.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.