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/commands/cekura-ai/cekura-skills/cekura-results-report)<a href="https://agentmods.dev/commands/cekura-ai/cekura-skills/cekura-results-report"><img src="https://agentmods.dev/badge/commands/cekura-ai/cekura-skills/cekura-results-report/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/commands/cekura-ai/cekura-skills/cekura-results-report"><img src="https://agentmods.dev/badge/commands/cekura-ai/cekura-skills/cekura-results-report.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.00047 | $0.00743 |
| Opus 5.5 | $0.00019 | $0.00297 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
cekura-results-report 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 19d 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
Tracking (do this first)
Before doing anything else, call mcp__cekura__cekura_skill_started with
skill_name="cekura-results-report". If a conversation/session ID is available (e.g. you
were invoked from Cekura sandbox), also pass it as conversation_id. The call
returns immediately; it lets us understand which skills are actually being used.
If anything in this skill turns out to be ambiguous, broken, or missing a
needed tool, call mcp__cekura__cekura_report_issue to flag it. Use this
LIBERALLY — even severity="low" reports are valuable feedback.
/cekura-results-report
Design a client-ready report on test results that already exist, shaped by what the user asks. Read-only: never generate scenarios, run tests or change anything.
Arguments: $ARGUMENTS — an agent (ID or name) and what the report should answer, e.g. /cekura-results-report 12345 how responsive is the agent?.
Process
- Load the skill. Invoke the
cekura:cekura-results-reportskill viaSkilland follow it — its flow, references and quality check. (Its tracking call is covered by the one above; don't repeat it.) - Clarify only what blocks you. If the agent(s) or the period are unclear, ask once with
AskUserQuestion(choices such as "Last 14 days / Last 30 days / Pick results"); usemcp__cekura__aiagents_listto resolve an agent name. Defaults when the user says "go ahead": all agents, the last 14 days, all test results in the period. - Redirect when it's the other kind of request. Testing an agent from scratch →
/cekura-report. - Reply with a 3–5 line chat summary, the report as one JSON block between
<!-- CEKURA-V0-REPORT-START -->and<!-- CEKURA-V0-REPORT-END -->, and the line "Open the report above, or use Download PDF on it." Run the skill's quality check before sending.
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.
- 19d ago First seen · 51 lines · 47 tokens per session scan A a8963f19ab91
cekura-results-report is a command published in the GitHub repository cekura-ai/cekura-skills (8 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 743 once invoked, about $0.0002 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-10.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.