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 cekura-ai/cekura-skills --skill cekura-coordinatorgit clone --depth 1 https://github.com/cekura-ai/cekura-skillsWrote 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/cekura-ai/cekura-skills/cekura-coordinator)<a href="https://agentmods.dev/skills/cekura-ai/cekura-skills/cekura-coordinator"><img src="https://agentmods.dev/badge/skills/cekura-ai/cekura-skills/cekura-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/cekura-ai/cekura-skills/cekura-coordinator"><img src="https://agentmods.dev/badge/skills/cekura-ai/cekura-skills/cekura-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.00097 | $0.02564 |
| Opus 5 | $0.00048 | $0.01282 |
| Sonnet 5 | $0.00019 | $0.00513 |
| Haiku 4.5 | $0.00010 | $0.00256 |
Grade A, and why
cekura-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 yesterday.
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cekura Coordinator
Purpose
Route users to the right Cekura skill or command based on what they need. This is the "front desk" — it knows everything available across all Cekura plugins and helps users find the right tool.
Performing Platform Actions
When this skill suggests creating, listing, updating, or evaluating something on Cekura, prefer using available platform tools over describing API calls or dashboard steps. In Claude Code with the Cekura plugin installed, these tools are auto-configured and handle authentication, parameter validation, and error handling for you. Fall back to direct API endpoints or dashboard guidance only when no tools are available in the current session.
When This Skill Loads
- User just installed cekura-skills and asks "what can I do?"
- User asks for help or doesn't know which command to use
- User describes a task and you need to route them
Available Skills & Commands
Skills activate when the user describes a relevant task. Commands are slash commands available only in Claude Code with the plugin installed.
Skills
| Skill | Use when |
|---|---|
cekura-onboarding |
New to Cekura, first-time setup, platform walkthrough |
cekura-create-agent |
Set up a voice AI agent — provider, mock tools, KB, dynamic vars |
cekura-self-improving-agent |
Auto-tune agent prompts from eval results — diagnose → propose → apply → re-validate |
cekura-metric-design |
Design new metrics, improve existing ones, metric best practices |
cekura-metric-improvement |
Improve metric accuracy through feedback cycle (labs workflow) |
cekura-predefined-metrics |
Catalog of built-in metrics — what each does, costs, constraints, configuration |
cekura-eval-design |
Design evaluators, test suites, coverage strategy, conditional actions |
cekura-personality-design |
Choose, fork or create a personality — the simulated caller's voice, accent, speed, interruption and idle behavior |
cekura-infra-test-suite |
Source-controlled JSON Tests-as-Code suite — repository discovery, deterministic CI coverage, safe dry-run validation |
cekura-bot-test-writer |
Keep that committed suite in step with the code — read a PR diff, edit the smallest thing that closes a real gap |
cekura-flag-call-log-failures |
Triage recent production call logs against KPIs — failure rates + outcome distribution |
cekura-generate-scenarios |
Turn flagged production failures into regression evaluator scenarios |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +3 lines 85c052604b9d
- 2d ago Changed · +1 lines 852e8fdabf86
- 8d ago Changed · +1 lines ec601bc0c86f
- 12d ago First seen · 160 lines · 97 tokens per session scan A 34e332b2d80e
cekura-coordinator is a skill published in the GitHub repository cekura-ai/cekura-skills (7 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 2,564 once invoked, about $0.0005 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-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.