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 mdelapenya/coding-skills --skill ci-detectivegit clone --depth 1 https://github.com/mdelapenya/coding-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/mdelapenya/coding-skills/ci-detective)<a href="https://agentmods.dev/skills/mdelapenya/coding-skills/ci-detective"><img src="https://agentmods.dev/badge/skills/mdelapenya/coding-skills/ci-detective.svg" alt="Measured on agentmods" 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.00078 | $0.00854 |
| Opus 5 | $0.00039 | $0.00427 |
| Sonnet 5 | $0.00016 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
ci-detective 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Detective
Investigate CI failures on a PR by cross-referencing failing tests against other recent runs to determine whether failures are pre-existing or introduced by the PR.
Do not assume failures are pre-existing or infrastructure-related. Always gather evidence first.
Supported CI Systems
This skill supports multiple CI platforms. Each platform has its own reference file under references/ with platform-specific commands and patterns.
Currently supported:
- GitHub Actions — see
references/github-actions.md - GitLab CI — see
references/gitlab-ci.md
Planned:
- Jenkins
When investigating, first detect which CI system the repository uses, then load the corresponding reference file for platform-specific commands.
Arguments
$1— Number of recent runs to query (default: 10). Example:/ci-detective 20
Workflow
Step 1: Detect the CI system
Check the repository for CI configuration:
.github/workflows/→ GitHub Actions (loadreferences/github-actions.md).gitlab-ci.yml→ GitLab CI (loadreferences/gitlab-ci.md)
If the CI system is not yet supported, inform the user and stop.
Step 2: Get failing job and test names from the current PR's run
Using the platform-specific commands from the loaded reference, identify the current branch's PR and its most recent failing workflow run. Record the workflow name, failing job names, and failing test names.
Step 3: Find recent completed runs of the same workflow on other branches
Query the last $1 runs (default: 10) and filter to completed runs on branches other than the current PR's branch. Select 3–5 from the results with a mix of conclusions (prefer at least one passing and one failing if available).
Step 4: Check if the same jobs/tests fail in those runs
For each selected run, check whether the same jobs failed. If a job failed in another run, fetch its logs to confirm the same test is failing.
Step 5: Classify each failure
What ships with it
2 files 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.
- 7d ago First seen · 85 lines · 78 tokens per session scan A e2427d73e458
ci-detective is a skill published in the GitHub repository mdelapenya/coding-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 78 tokens to every session and 854 once invoked, about $0.0004 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
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
github-ci-fix
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
github-ci-fix
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.