Borrowing it
Nothing to install: this file belongs to victoriacity/openakari. 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/victoriacity/openakari/main/.claude/skills/coordinator/SKILL.mdgit clone --depth 1 https://github.com/victoriacity/openakariWrote 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/victoriacity/openakari/coordinator)<a href="https://agentmods.dev/skills/victoriacity/openakari/coordinator"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/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/victoriacity/openakari/coordinator"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/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.00025 | $0.01861 |
| Opus 5.5 | $0.00010 | $0.00744 |
| Sonnet 5.5 | $0.00005 | $0.00372 |
| Haiku 4.5 | $0.00003 | $0.00186 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/coordinator
Detailed operational guidance for Akari's Slack bot. The action-tag syntax is provided in the chat prompt — this skill has extended guidance on experiment launches, status queries, and procedures.
Available actions
Include EXACTLY ONE action tag at the END of your message when the user wants to perform an operation:
Approvals
[ACTION:approve item=N notes="optional"]
[ACTION:deny item=N notes="optional"]
Where N is the 1-based item number from the approval list. These require user confirmation.
Session supervision
[ACTION:stop_session id="<session-id>"]
[ACTION:ask_session id="<session-id>" message="<question>"]
[ACTION:watch_session id="<session-id>"]
These execute immediately (no confirmation needed).
Experiments
[ACTION:launch_experiment project="<p>" id="<id>" command="<cmd>"]
[ACTION:stop_experiment project="<p>" id="<id>"]
launch_experiment requires user confirmation. stop_experiment executes immediately.
Jobs
[ACTION:run_job id="<job-id>"]
Triggers a scheduled job immediately. Use the job ID from the Jobs context. Requires user confirmation.
Deep work
[ACTION:deep_work task="<self-contained task description>"]
Spawns an opus agent session (~20 min, 256 turns) for tasks that exceed chat scope.
Use when the user's request requires sustained research, multi-file analysis, writing, or implementation.
The task description must be self-contained — the deep work agent has no conversation history.
Confirmation required when:
- User's intent is ambiguous or could be interpreted multiple ways
- Request spans multiple possible approaches or outcomes
- You're uncertain about the exact scope or goal
Before dispatching, show the user:
- A brief summary of what you understand the task to be
- The specific task description you'll send to the deep work agent
- Ask: "Does this capture what you need? I'll launch a 20-min agent session with this task."
If the user confirms or intent is clear from context → dispatch immediately. If ambiguous → summarize first and wait for confirmation.
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.
- 2mo ago First seen · 128 lines · 25 tokens per session scan A 83d04bc5e3d8
coordinator is a skill published in the GitHub repository victoriacity/openakari (47 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 1,861 once invoked, about $0.0001 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.