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 andisab/swe-marketplace --skill coordinatorgit clone --depth 1 https://github.com/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/coordinator)<a href="https://agentmods.dev/skills/andisab/swe-marketplace/coordinator"><img src="https://agentmods.dev/badge/skills/andisab/swe-marketplace/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/skills/andisab/swe-marketplace/coordinator"><img src="https://agentmods.dev/badge/skills/andisab/swe-marketplace/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.00183 | $0.02583 |
| Opus 5.5 | $0.00073 | $0.01033 |
| Sonnet 5.5 | $0.00037 | $0.00517 |
| Haiku 4.5 | $0.00018 | $0.00258 |
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 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.
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are executing the research-team plugin's multi-agent research pipeline in the main agent context. Your job is to orchestrate — never research or write yourself.
CRITICAL RULES:
- You MUST delegate ALL research and report writing to the plugin's specialist subagents. You NEVER research or write reports yourself.
- Keep your own responses to 2-3 sentences max. No greetings, no emojis, no meta-commentary.
- Spawn researcher subagents IN PARALLEL via multiple Task tool calls in a single response — never sequentially.
- Wait for ALL researchers to return before spawning the report-writer.
- Trust nothing you didn't verify. Every claimed output file must be confirmed on disk via
Globbefore you tell the user the work is done.
Why this is a skill, not an agent
Claude Code agents are always spawned as subagents. An agent that itself needs to spawn subagents via Task hits Claude Code's nested-spawn constraint and fails. This skill runs in the main agent's context, so its Task calls are first-level and succeed. Do not attempt to delegate this orchestration back to a subagent — run it here.
Available tools in this workflow
- Task: Spawn
research-team:research-specialistandresearch-team:research-report-writersubagents. Primary tool. Always use the fully-qualified plugin-namespaced form forsubagent_type— bare names fail to resolve across plugin boundaries. - Bash(mkdir:*): Run exactly ONE command per session to ensure the working directories exist:
mkdir -p ~/Documents/Claude/Research/research_notes ~/Documents/Claude/Research/reports. Idempotent. Do not issue any other Bash call — your scope only permitsmkdir. - Glob: Primary verification tool — confirm that researchers' claimed output paths and the report-writer's output actually exist on disk.
- Read: Escape hatch only — for diagnosing a malformed output manifest. Do NOT read research notes and summarize them yourself; that violates the delegation rule.
Workflow
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 · 171 lines · 183 tokens per session scan A 63bc268fd62c
coordinator is a skill published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed today), licensed MIT. It adds 183 tokens to every session and 2,583 once invoked, about $0.0007 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-17.
Other skills, from other repositories
ccc-tuneup
Audit and safely optimize the local Commander setup: version freshness, junk, count drift, superseded agents, hooks, settings keys, MCP staleness and cost settings. Read-only scan first; backs up, archives (never deletes) and asks before any fix. Use when the setup feels cluttered, stale or slow.
ccc-adopt
Merge Commander's orchestrator/executor section and a stack-tailored skill and agent list into an existing project's CLAUDE.md as a delimited, re-runnable block, with backup and diff approval first. Use when adopting Commander conventions in a repo you already have.
ccc-fable
Arm, check, audit or disarm the Fable Method: the PM loop, 12 checkable gates, workflow-first posture and verifier separation, persisted in Commander state. Use when the user says fable on/off/status/audit or wants verification-gated, orchestrated work.
ccc-codex
Manage the OpenAI Codex CLI: doctor, models, plugins, MCP servers, custom agents, cloud tasks, remote control, reviews, updates, import and config, backing up config first. Use when the user asks to check, set up or manage Codex.
ccc-deploy
Deploy the current build to Vercel, Fly.io, Cloudflare, GitHub Pages, npm, or a package deploy script, verify the live URL, and draft post-deploy notes. Use when a build is ready to go live or the user says deploy, push to production, or publish the package.
ccc-e2e
Pre-release assessment that fans out via $ccc-fleet into up to three isolated workers (QA audit, unit tests, Playwright E2E) running $ccc-testing lanes, then writes a severity-ranked PASS or FAIL verdict. Use when about to tag a release, after a large merge, or asking is this ready.