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-generate-scenariosgit 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-generate-scenarios)<a href="https://agentmods.dev/skills/cekura-ai/cekura-skills/cekura-generate-scenarios"><img src="https://agentmods.dev/badge/skills/cekura-ai/cekura-skills/cekura-generate-scenarios/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-generate-scenarios"><img src="https://agentmods.dev/badge/skills/cekura-ai/cekura-skills/cekura-generate-scenarios.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00234 | $0.11514 |
| Opus 5 | $0.00117 | $0.05757 |
| Sonnet 5 | $0.00047 | $0.02303 |
| Haiku 4.5 | $0.00023 | $0.01151 |
Grade A, and why
cekura-generate-scenarios 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cekura skill verification tag:
ack:cekura-generate-scenarios:7q3n6vWhen you call a Cekura scenario or test-profile write tool from this skill (scenarios_*/test_profiles_*create and update calls), pass this exact string as theskill_ackargument on that tool call. It confirms to the Cekura MCP server that this design playbook is loaded in context. Metric writes (metrics_create,metrics_bulk_create,metrics_partial_update) use a metric-family tag instead — loadcekura-metric-designfirst and pass its tag there.
Before taking any action, call mcp__cekura__cekura_skill_started with skill_name="cekura-generate-scenarios", verification_tag="ack:cekura-generate-scenarios:7q3n6v", and plugin_version="0.16". It returns immediately and lets Cekura see which skills are in use.
generate-scenarios
Convert real production failures into evaluator scenarios so the next regression run catches them. Signal is mined from call logs — what real callers did, where the agent broke, and what the right behavior would have been. Every scenario produced traces back to at least one call log; nothing is invented.
This skill is read-first: it never creates a scenario without an explicit user OK on the proposed set.
Write path — decided by scenario_type, not by preference
scenario_type |
Write path |
|---|---|
conditional_actions — drop, tool_error, workflow_miss (turn-by-turn replays) |
mcp__cekura__scenarios_create with the drafted conditions — the evidence call dictates the turn sequence, which is the one case that outranks generation. When you have the failure mode but not the turns, scenarios_generate_bg with simulation_type: "conditional_actions" emits grounded, validated conditions. |
instruction — drift, hallucination, comprehension, refusal, safety (free-form) |
Generate: mcp__cekura__call_logs_create_scenarios (preferred — grounded in the evidence calls) or scenarios_generate_bg, passing the drafted expected_behavior + failure mode as extra_instructions. Behavioral instructions are never hand-authored. |
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 6897264e813c
- 3d ago Changed 23f6234972ed
- 8d ago Changed bd6d3f54b7f2
- 12d ago First seen · 499 lines · 234 tokens per session scan A b22bbcbb9224
cekura-generate-scenarios is a skill published in the GitHub repository cekura-ai/cekura-skills (7 stars, last pushed yesterday), licensed MIT. It adds 234 tokens to every session and 11,514 once invoked, about $0.0012 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
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…