Creek-Vault: Skill for Claude Code

.claude/skills/ci-debugging/SKILL.md

ci-debugging is a skill for Claude Code from Geoffe-Ga/Creek-Vault. It costs 68 tokens per session (981 once invoked), scanned A, original, no licence file.

A structured aid for investigating failed continuous-integration checks on pull requests. Continuous integration, or CI, automatically builds and tests code on a shared service.

In plain words
What is it for?
Use it when tests fail on a pull request, when they pass locally but fail in CI, or when you need to reproduce and diagnose the failure.
Why use it?
It helps distinguish code problems, environment differences and misleading assumptions such as calling a failure pre-existing.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Geoffe-Ga/Creek-Vault's own configuration. It tells Claude Code how to work on Creek-Vault itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Creek-Vault configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Geoffe-Ga/Creek-Vault. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Geoffe-Ga/Creek-Vault/main/.claude/skills/ci-debugging/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Geoffe-Ga/Creek-Vault

Made for: Claude Code.

Wrote 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.

agentmods badge for ci-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/geoffe-ga/creek-vault/ci-debugging/github.svg)](https://agentmods.dev/skills/geoffe-ga/creek-vault/ci-debugging)
Your own site
<a href="https://agentmods.dev/skills/geoffe-ga/creek-vault/ci-debugging"><img src="https://agentmods.dev/badge/skills/geoffe-ga/creek-vault/ci-debugging/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.

agentmods 80×15 button for ci-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/geoffe-ga/creek-vault/ci-debugging"><img src="https://agentmods.dev/badge/skills/geoffe-ga/creek-vault/ci-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 981 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.00981
Opus 5.5 $0.00027 $0.00392
Sonnet 5.5 $0.00014 $0.00196
Haiku 4.5 $0.00007 $0.00098

Measured 2mo ago against content hash e6a8dfa71dcb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ci-debugging 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 2mo 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.

.claude/skills/ci-debugging/SKILL.md · 139 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2mo ago First seen · 139 lines · 68 tokens per session scan A e6a8dfa71dcb

Subscribe to this mod's changes

ci-debugging is a skill published in the GitHub repository Geoffe-Ga/Creek-Vault (2 stars, last pushed 2d ago), with no licence file. It adds 68 tokens to every session and 981 once invoked, about $0.0003 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-08-31.

Related

Other skills, from other repositories

repair-github-ci

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.

Tracer-Cloud/opensre · 40 tokens

mcore-create-issue

Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.

NVIDIA/skills · 26 tokens

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, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…

moonrepo/moon · 203 tokens

operating-github-ci-fixer

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.

Tracer-Cloud/opensre · 48 tokens

meta-long-running-build-watchdog

Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.

opensquilla/opensquilla · 131 tokens

gh-fix-ci

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

foryourhealth111-pixel/Vibe-Skills · 72 tokens