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/report-bug)<a href="https://agentmods.dev/commands/cekura-ai/cekura-skills/report-bug"><img src="https://agentmods.dev/badge/commands/cekura-ai/cekura-skills/report-bug/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/report-bug"><img src="https://agentmods.dev/badge/commands/cekura-ai/cekura-skills/report-bug.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.00019 | $0.01450 |
| Opus 5 | $0.00010 | $0.00725 |
| Sonnet 5 | $0.00004 | $0.00290 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade B, and why
report-bug scanned grade B with 2 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 12d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
tail -20 ~/.claude/cekura-mcp-failures.log 2>/dev/null Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" https://api.cekura.ai/mcp 2>/dev/null || echo "unreachable" 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.
Tracking (do this first)
Before doing anything else, call mcp__cekura__cekura_skill_started with
skill_name="report-bug". 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.
Report a Cekura Skills Bug
Collect context about a bug the user encountered and file it as a GitHub issue on cekura-ai/cekura-skills. If the user doesn't have gh CLI, format the report for manual submission.
Process
1. Collect Bug Context
If the user didn't provide details in the arguments, ask:
- "What were you trying to do?" (which skill, command, or workflow)
- "What went wrong?" (error message, unexpected behavior, etc.)
2. Gather Environment Info Automatically
Run these (no need to narrate each one) to collect system context:
# Claude Code version
claude --version 2>/dev/null || echo "unknown"
# OS
uname -s -r
# Check if Cekura MCP server is reachable (production)
curl -s -o /dev/null -w "%{http_code}" https://api.cekura.ai/mcp 2>/dev/null || echo "unreachable"
# Check CEKURA_API_KEY is set (don't log the actual key)
[ -n "$CEKURA_API_KEY" ] && echo "API key: set" || echo "API key: NOT SET"
# Check marketplace repo state
cd ~/.claude/plugins/marketplaces/cekura-skills && git log --oneline -1 2>/dev/null
3. Check for Recent MCP Failure Logs
Look for the failure log that the hook writes to:
tail -20 ~/.claude/cekura-mcp-failures.log 2>/dev/null
If recent entries exist (within last 10 minutes), include them in the report. These give exact tool names and error messages.
Scrub before including. The log captures raw error/response text, which can echo request payloads, IDs, or credentials. Before putting any log excerpt into the issue body, redact anything secret-shaped: API keys and tokens (sk-..., Bearer ..., long hex/base64 runs), X-CEKURA-API-KEY values, email addresses, and phone numbers. Replace each with [REDACTED]. When unsure whether a value is sensitive, redact it — the maintainers can ask for details privately if needed.
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.
- 12d ago First seen · 165 lines · 19 tokens per session scan B fae1545b8cfb
report-bug is a command published in the GitHub repository cekura-ai/cekura-skills (7 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,450 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
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…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.