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 agentmods add skills/humansintheloop-dev/humansintheloop-dev-workflow-and-tools/debugging-ci-failuresnpx skills add humansintheloop-dev/humansintheloop-dev-workflow-and-tools --skill debugging-ci-failuresgit clone --depth 1 https://github.com/humansintheloop-dev/humansintheloop-dev-workflow-and-toolsWrote 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/humansintheloop-dev/humansintheloop-dev-workflow-and-tools/debugging-ci-failures)<a href="https://agentmods.dev/skills/humansintheloop-dev/humansintheloop-dev-workflow-and-tools/debugging-ci-failures"><img src="https://agentmods.dev/badge/skills/humansintheloop-dev/humansintheloop-dev-workflow-and-tools/debugging-ci-failures.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.00035 | $0.02087 |
| Opus 5 | $0.00017 | $0.01043 |
| Sonnet 5 | $0.00007 | $0.00417 |
| Haiku 4.5 | $0.00003 | $0.00209 |
Grade A, and why
debugging-ci-failures 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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago First seen · 214 lines · 35 tokens per session scan A 6bb9e320f355
debugging-ci-failures is a skill published in the GitHub repository humansintheloop-dev/humansintheloop-dev-workflow-and-tools (41 stars, last pushed 4d ago), with no licence file. It adds 35 tokens to every session and 2,087 once invoked, about $0.0002 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-30.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
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…
azdo-build-investigator
Investigate CI failures for dotnet/maui PRs and the nightly/official signed build — build errors, Helix test logs, and binlog analysis. Use when asked about failing checks, CI status, test failures, 'why is CI red', 'build failed', 'what's failing on PR', 'is this PR ready to merge', Helix failures, device test…
fix-ci
Check CI status, analyze test failures, auto-fix obvious issues or discuss with user.
ci-fix
Common safety and triage protocol for .NET MAUI CI-fixer workflows. Use whenever investigating, creating, or advancing a [ci-fix] or [ci-fix-net11] pull request from a ci-scan issue, including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual single-issue dispatches, and scheduled sweeps.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.