Synapse: Agent for Claude Code

.claude/agents/clear-orchestrator.md

clear-orchestrator is an agent for Claude Code from JosephOIbrahim/Synapse. It costs 144 tokens per session (1,360 once invoked), scanned A, original, MIT.

A coordinator for the CLEAR work-clearance harness, a project process for finding and resolving unfinished work. It organizes four review tracks and stops when a decision or human approval is required.

In plain words
What is it for?
Use it to sequence CLEAR reviews, dispatch the appropriate specialist agents, run the verifier, and pause at human approval gates.
Why use it?
It gives a structured way to review uncommitted work, unresolved decisions, release issues, and missing changelog entries without making the decisions itself.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is JosephOIbrahim/Synapse's own configuration. It tells Claude Code how to work on Synapse itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Synapse configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/JosephOIbrahim/Synapse/master/.claude/agents/clear-orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/JosephOIbrahim/Synapse

Made for: Claude Code.

Wrote 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.

agentmods badge for clear-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/josephoibrahim/synapse/clear-orchestrator/github.svg)](https://agentmods.dev/agents/josephoibrahim/synapse/clear-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/josephoibrahim/synapse/clear-orchestrator"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/clear-orchestrator/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.

agentmods 80×15 button for clear-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/josephoibrahim/synapse/clear-orchestrator"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/clear-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 144 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,360 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00144 $0.01360
Opus 5.5 $0.00058 $0.00544
Sonnet 5.5 $0.00029 $0.00272
Haiku 4.5 $0.00014 $0.00136

Measured 2mo ago against content hash db3e84c0d335, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/agents/clear-orchestrator.md · 97 lines

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

  1. 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).
  2. 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.
  3. 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.
  4. Match hands to breadth. Spawn hands only for independent lines that can run without blocking each other. Collapse them when the lines collapse.
  5. 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.

Read the full file on GitHub · 97 lines

Changes

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.

  1. 2mo ago First seen · 97 lines · 144 tokens per session scan A db3e84c0d335

Subscribe to this mod's changes

clear-orchestrator is an agent published in the GitHub repository JosephOIbrahim/Synapse (12 stars, last pushed today), licensed MIT. It adds 144 tokens to every session and 1,360 once invoked, about $0.0006 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.

Related

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.

athola/claude-night-market · 38 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

cso-agent

CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.

JOINCLASS/ai-ceo-framework · 27 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

goals-onboarding

Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…

41fred/ace-level1 · 206 tokens

status-reporter

Use this agent to generate a cross-project status dashboard showing all projects at a glance. Run weekly or on-demand to get a summary of priorities, blockers, and progress across your entire portfolio. Examples: Context: User wants a quick overview of all projects. user: "What's the status across all my projects?"…

41fred/ace-level1 · 172 tokens