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.
git 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/plugins/cekura-ai/cekura-skills/cekura)<a href="https://agentmods.dev/plugins/cekura-ai/cekura-skills/cekura"><img src="https://agentmods.dev/badge/plugins/cekura-ai/cekura-skills/cekura/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/plugins/cekura-ai/cekura-skills/cekura"><img src="https://agentmods.dev/badge/plugins/cekura-ai/cekura-skills/cekura.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cekura 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.
What it actually says
{
"name": "cekura",
"displayName": "Cekura",
"version": "0.16.0",
"description": "Cekura voice AI testing & evaluation \u2014 platform onboarding, agent setup, metric design and improvement, evaluator design and execution.",
"author": {
"name": "Cekura",
"email": "[email protected]",
"url": "https://cekura.ai"
},
"keywords": [
"cekura",
"voice-ai",
"evaluation",
"metrics",
"evaluators",
"testing",
"scenarios",
"onboarding",
"platform"
],
"homepage": "https://docs.cekura.ai/mcp/overview",
"repository": "https://github.com/cekura-ai/cekura-skills",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 13 skills, 14 commands, 3 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 2,483 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill cekura-eval-design A 234 tokens
- Skill cekura-generate-scenarios A 234 tokens
- Skill cekura-infra-test-suite A 140 tokens
- Skill cekura-bot-test-writer A 172 tokens
- Skill cekura-flag-call-log-failures A 229 tokens
- Skill cekura-personality-design A 176 tokens
- Skill cekura-metric-improvement A 80 tokens
- Skill cekura-predefined-metrics A 121 tokens
- Skill cekura-self-improving-agent A 189 tokens
- Skill cekura-coordinator A 97 tokens
- Skill cekura-onboarding A 156 tokens
- Skill cekura-metric-design B 136 tokens
- Skill cekura-create-agent C 197 tokens
- Command cekura-report A 31 tokens
- Command autogen-eval A 20 tokens
- Command manual-create-update-eval A 37 tokens
- Command cekura-onboarding A 43 tokens
- Command improve-metric A 22 tokens
- Command eval-results A 14 tokens
- Command upgrade-skills A 16 tokens
- Command run-evals A 35 tokens
- Command evaluate-calls A 19 tokens
- Command list-evals A 18 tokens
- Command list-metrics A 14 tokens
- Command report-bug B 19 tokens
- Command setup-mcp B 16 tokens
- Command create-metric B 18 tokens
- Hook PostToolUseFailure A not measured
- Hook PreToolUse A not measured
- Hook SessionStart A not measured
- MCP server cekura A not measured
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 Changed 3de5461fb5eb
- yesterday Changed 72935a8bbee3
- 2d ago Changed b3c217325186
- 3d ago Changed 697e17a96176
- 4d ago Changed a5b0fed3f076
- 5d ago Changed df523bcd2eaa
- 7d ago Changed 86dfbfefd7d0
- 8d ago Changed 1abd651169b6
- 12d ago First seen · 26 lines scan A 7668dc7a64f2
cekura is a plugin published in the GitHub repository cekura-ai/cekura-skills (7 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
load-tester
Load and stress testing for APIs and web services.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
looptimal
Turns an objective into a delivered, VERIFIED OUTCOME: frames a hash-pinned sealed acceptance suite, designs the right loop (the loop-design wizard, formerly LoopPrint), war-games it forward, executes with dynamic domain-expert sub-agents (maker != checker), and gates completion on a separate verifier re-running the…
pict-test-designer
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for any piece of requirements or code. Analyzes inputs, generates PICT models with parameters, values, and constraints for valid scenarios using pairwise testing. Outputs the PICT model, markdown table of test cases, and expected…
local-test-plugin
Symlink-based local plugin testing for development workflow.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.