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 skills add hogancv/coordinate-agents --skill coordinate-recovergit clone --depth 1 https://github.com/hogancv/coordinate-agentsWrote 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/skills/hogancv/coordinate-agents/coordinate-recover)<a href="https://agentmods.dev/skills/hogancv/coordinate-agents/coordinate-recover"><img src="https://agentmods.dev/badge/skills/hogancv/coordinate-agents/coordinate-recover/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/skills/hogancv/coordinate-agents/coordinate-recover"><img src="https://agentmods.dev/badge/skills/hogancv/coordinate-agents/coordinate-recover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00883 |
| Opus 5 | $0.00022 | $0.00441 |
| Sonnet 5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
coordinate-recover 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 9d 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
Coordinate Recover
Use coordinate_agents_recover_inspect,
coordinate_agents_task_status, and coordinate_agents_task_resume for
single-Task recovery. For a Task Graph, use
coordinate_agents_task_graph_recover, coordinate_agents_task_graph_resume,
coordinate_agents_task_graph_stop, and
coordinate_agents_task_graph_cleanup. Recovery is facts-first and never an
automatic retry.
If MCP is unavailable, or the user explicitly requests debugging, let
<skill-dir> be the absolute directory containing this loaded SKILL.md and
use the bundled fallback:
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" ...
The normal Plugin path starts with coordinate_agents_recover_inspect, followed
by coordinate_agents_task_status or coordinate_agents_task_resume only when
the recovery decision requires them. The following commands are fallback/debug
syntax only:
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task status --root "<repository>" --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" status --root "<repository>" --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" agent doctor --root "<repository>" --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task graph-recover --root "<repository>" --id task-... --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task graph-resume --root "<repository>" --id task-... --subtask <subtaskId> --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task graph-stop --root "<repository>" --id task-... --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task graph-cleanup --root "<repository>" --id task-... --json
Inspect the Task's lastError, the bounded runtime artifact, Agent Bus state,
the sessionId Session status/inspect facts, and any matching commit or
evidence. Explain the concrete error code and the smallest repair. Session
inspection is read-only: do not restart, replay input, attach to a different
PID, or resume the Task while collecting facts. Do not claim a missing
capability as a successful result.
Only after the user explicitly asks to continue, invoke:
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task resume --root "<repository>" --id task-... --json
task resume only clears the explicit recovery gate; it does not launch an
Implementer. After the user confirms the repair, use task dispatch so the
Task API performs executable validation, Bus handoff, launch, and state/error
propagation as one operation.
For graph recovery, task graph-recover inspects durable Session, worktree,
commit, and evidence records and records an interrupted FAILED subtask only
when no healthy Session or verified completion exists. It never infers success
from filenames or prose. task graph-resume is a separate explicit decision:
it reuses a verified healthy Runtime-owned Session/worktree, or returns an
exited/failed Session to READY for a later explicit graph dispatch. Failed
prerequisites keep dependents BLOCKED until this valid recovery path runs.
Use task graph-stop to mark active graph work STOPPED and close only
Runtime-owned Sessions, followed by task graph-cleanup when needed. Both
operations use bounded, ownership-checked cleanup and preserve user worktrees,
branches, refs, commits, and evidence; repeated recovery/resume/stop/cleanup
calls are idempotent.
TASK_NOT_FOUND, STALE_CLAIM, AGENT_EXIT_NONZERO, AGENT_TIMEOUT, and
AUTH_REQUIRED remain facts to report; they do not authorize silent retries.
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.
- 9d ago First seen · 74 lines · 43 tokens per session scan A 919511bd97e0
coordinate-recover is a skill published in the GitHub repository hogancv/coordinate-agents (102 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 883 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Methodical problem-solving approach for diagnosing and resolving code issues in any stack before attempting a fix.
threat-intel-triage
Identifies indicators of compromise, anomalous network/endpoint behavior, and active intrusion patterns from the provided data.
adk-debug
Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…
backtest-diagnose
Diagnose failed or underperforming backtests, locate the root cause, and fix the issue.
oma-debug
Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Use for bug, debug, error, crash, traceback, exception, and regression work.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.