Borrowing it
Nothing to install: this file belongs to Chia-Network/cadt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Chia-Network/cadt/develop/.cursor/skills/gh-ci-debugging/SKILL.mdgit clone --depth 1 https://github.com/Chia-Network/cadtWrote 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/chia-network/cadt/gh-ci-debugging)<a href="https://agentmods.dev/skills/chia-network/cadt/gh-ci-debugging"><img src="https://agentmods.dev/badge/skills/chia-network/cadt/gh-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.
<a href="https://agentmods.dev/skills/chia-network/cadt/gh-ci-debugging"><img src="https://agentmods.dev/badge/skills/chia-network/cadt/gh-ci-debugging.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.00055 | $0.02463 |
| Opus 5.5 | $0.00022 | $0.00985 |
| Sonnet 5.5 | $0.00011 | $0.00493 |
| Haiku 4.5 | $0.00006 | $0.00246 |
Grade A, and why
gh-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 1mo 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging CADT CI with gh
Required: Deep investigation before reporting
Do NOT conclude "infrastructure flakiness" or recommend "re-run" without completing ALL of these:
-
Read CADT server logs, not just test output. Test output shows symptoms (timeouts, assertion failures). CADT logs show causes (process failures, wallet errors, store creation errors). Always run:
gh run view --log --job <JOB_ID> 2>&1 | grep "Show CADT logs after" -A 5000 | grep -iE "error|failed|removing" -
Build a timeline. Extract timestamps for: when the operation started, when errors occurred, when the test gave up. If the error happened early but the test ran for 20+ more minutes, the test couldn't detect the failure — that's a bug, not flakiness.
-
Check if transient errors recovered. If you see wallet sync errors, check the end-of-job wallet status (
Show wallet balancestep). If the wallet is synced at job end but the operation failed mid-job, the error was transient and the code should have retried. -
Read the source code for the failing operation. Check whether it has retry logic,
waitForSpendableCoins()calls, or error handling for transient wallet errors. Compare to similar operations that DO work (e.g.,createV2OrganizationvsupgradeFromV1). -
Never recommend "re-run" as the primary action. If investigation reveals a code-level gap (missing retry, missing wallet check, broken fast-fail logic), that's a bug to fix — not flakiness to retry past.
CI Jobs Overview
The .github/workflows/tests.yaml workflow has 5 parallel jobs:
| Job name | Job key | What it tests | npm script(s) |
|---|---|---|---|
| v1 integration tests | test-v1 |
Unit/integration (simulator) | npm run test:v1 |
| v2 integration tests | test-v2 |
Unit/integration (simulator) | npm run test:v2 |
| v2 live api tests | test-v2-live-api |
E2E with real Chia + datalayer | See below |
| v1 live api tests | test-v1-live-api |
E2E with real Chia + datalayer | See below |
| v1 to v2 upgrade test | test-v1-to-v2-upgrade |
V1 org creation then upgrade to V2 | npm run test:v1:live:organization:upgrade |
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.
- 1mo ago First seen · 201 lines · 55 tokens per session scan A b8b97c345dc6
gh-ci-debugging is a skill published in the GitHub repository Chia-Network/cadt (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 2,463 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-09-04.
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.
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, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
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.
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.
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.