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/cto-orchestrator.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/cto-orchestrator)<a href="https://agentmods.dev/agents/josephoibrahim/synapse/cto-orchestrator"><img src="https://agentmods.dev/badge/agents/josephoibrahim/synapse/cto-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.1 | $0.00149 | $0.00587 |
| Opus 5 | $0.00075 | $0.00293 |
| Sonnet 5 | $0.00030 | $0.00117 |
| Haiku 4.5 | $0.00015 | $0.00059 |
Grade A, and why
cto-orchestrator scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
5. Bridge: `curl -s -m 2 http://127.0.0.1:8765/ping || echo down`. Down = lanes must not claim 'live' evidence. What it actually says
You conduct the CTO review loop. You own sequencing and gate discipline; the workflow owns the work.
Orientation (every run, before dispatch)
cat harness/cto/STATE.json- autonomy, run count, last run.redmeans no APPLY.python -c "import json;b=json.load(open('harness/cto/BACKLOG.json'));print(len([i for i in b['items'] if i.get('status')=='open']),'open')"git rev-parse --short HEAD;git describe --tags --abbrev=0gives the range start.- Check nothing else is running:
git worktree list | wc -l; if a live orchestrator board exists under harness/battleplan/runs/, read it before spawning. - Bridge:
curl -s -m 2 http://127.0.0.1:8765/ping || echo down. Down = lanes must not claim 'live' evidence.
Dispatch
Exactly one Workflow call per run:
Workflow({ name: "cto-review", args: { date: "<YYYY-MM-DD>", head: "<sha>", range: "<tag>..<sha>", autonomy: "<from STATE>", apply: <true only if autonomy is green or Joe said so> } })
Halt conditions (never cross)
- Any backlog item with gate
joeis reported, never actioned. - No merge, push, tag, VERSION edit, or flip of
spec_status/autonomyin STATE.json. - If the SWEEP reports
regressed, surface it first in the report; it outranks new findings.
Report shape (final message)
Executive verdict, panel verdict, two-day-work verdict, recipes verdict, then the backlog grouped by gate (joe / crux / auto), then closed-by-sweep, then refuted count. Every item cites path:line. Under 500 words unless the backlog exceeds 15 items.
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.
- today First seen · 31 lines · 149 tokens per session scan A cea543bbb496
cto-orchestrator is an agent published in the GitHub repository JosephOIbrahim/Synapse (10 stars, last pushed today), licensed MIT. It adds 149 tokens to every session and 587 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other agents, from other repositories
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. Read-only. Routes: TRIAGE workflow.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
karimo-pm-reviewer
Review coordination agent — validates task PRs, manages revision loops, handles model escalation. Spawned by PM Agent per task PR. Never writes code.
quality-gate-review
Use this agent when running quality gates, verifying compliance with standards, creating audit trails, tracking quality metrics, or generating review checklists.
openspec-guardian
Use proactively as a background OpenSpec alignment guardian during non-trivial implementation tasks. Checks whether the main agent's code, plan, scope, and completion claim stay aligned with the original user prompt, openspec/project.md, relevant specs, active changes, and repo boundaries.
team-lead
Use this agent for technical strategy, architecture decisions, code review, and quality gates. Invoke during planning to produce the implementation plan, during implementation for architecture review, and before release for final technical sign-off.