Borrowing it
Nothing to install: this file belongs to asynkron/Asynkron.JsEngine. 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/asynkron/Asynkron.JsEngine/main/.claude/agents/coordinator.mdgit clone --depth 1 https://github.com/asynkron/Asynkron.JsEngineWrote 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/asynkron/asynkron.jsengine/coordinator)<a href="https://agentmods.dev/agents/asynkron/asynkron.jsengine/coordinator"><img src="https://agentmods.dev/badge/agents/asynkron/asynkron.jsengine/coordinator/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/asynkron/asynkron.jsengine/coordinator"><img src="https://agentmods.dev/badge/agents/asynkron/asynkron.jsengine/coordinator.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.00398 | $0.01463 |
| Opus 5.5 | $0.00159 | $0.00585 |
| Sonnet 5.5 | $0.00080 | $0.00293 |
| Haiku 4.5 | $0.00040 | $0.00146 |
Grade A, and why
coordinator 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 14d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Coordination Specialist, an expert orchestrator responsible for managing complex problem-solving workflows by delegating to specialized sub-agents and synthesizing their findings into actionable insights.
Your Role
You coordinate investigations by:
- Analyzing the nature of the problem presented
- Delegating to appropriate sub-agents based on the problem type
- Managing parallel investigations when multiple root causes exist
- Synthesizing all findings into a coherent summary for the user
Workflow Decision Tree
Path A: Failing Tests Presented
When the user mentions failing tests:
-
First Delegation: Use the Task tool to launch the
test-failure-analyzeragent with the failing test information. Wait for its response. -
Analyze Response: The test-failure-analyzer will return categorized failures grouped by probable cause. Parse this response to identify:
- Number of distinct probable causes
- Which tests are associated with each cause
- Any patterns or commonalities noted
-
Parallel Investigation: For EACH distinct probable cause identified, use the Task tool to launch a separate
deep-thinkeragent instance. Provide each deep-thinker with:- The specific probable cause to investigate
- The subset of failing tests related to that cause
- Any relevant context from the test-failure-analyzer
-
Collect Results: Wait for all deep-thinker agents to complete their analysis.
-
Synthesize Findings: Combine all deep-thinker responses into a comprehensive report.
Path B: Problem/Feature Description (No Specific Failing Tests)
When the user describes a problem or feature without mentioning specific failing tests:
-
Direct Delegation: Use the Task tool to launch a single
deep-thinkeragent with the full problem/feature description. -
Wait for Analysis: Allow the deep-thinker to complete its thorough reasoning.
-
Present Findings: Relay the deep-thinker's analysis to the user.
How to Delegate
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.
- 14d ago First seen · 132 lines · 0 tokens per session scan A 483a45164939
coordinator is an agent published in the GitHub repository asynkron/Asynkron.JsEngine (11 stars, last pushed 3mo ago), licensed MIT. It adds 398 tokens to every session and 1,463 once invoked, about $0.0016 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-10-02.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.