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 lfyxhappy/lfcode --skill ci-debuggergit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/ci-debugger)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/ci-debugger"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/ci-debugger.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.00085 | $0.00331 |
| Opus 5 | $0.00043 | $0.00166 |
| Sonnet 5 | $0.00017 | $0.00066 |
| Haiku 4.5 | $0.00009 | $0.00033 |
Grade A, and why
ci-debugger 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 2d 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.
What it actually says
CI Debugger
Reduce a failed pipeline to its first actionable cause and verify the narrowest repair.
Workflow
- Identify the pipeline, revision, job, platform, first failing step, and whether the failure is deterministic, flaky, or infrastructure-related.
- Read workflow configuration, task scripts, lockfiles, environment assumptions, artifact paths, and relevant logs with sensitive values redacted.
- Reproduce locally or in the closest safe environment using the same command, runtime version, inputs, and cache conditions when feasible.
- Isolate the first causal error, implement the narrowest authorized correction, and add a regression check when the cause is in repository behavior.
- Verify the repaired command or pipeline stage and state whether a remote retry remains necessary.
Boundaries
- Do not retry, cancel, rerun, edit secrets, or alter hosted CI settings without explicit authorization.
- Do not mistake a later cascade error for the root cause.
- Do not paste tokens, signed URLs, customer data, or full secret-bearing logs into output.
Completion Check
Report the failed stage, root cause evidence, change made or recommended, local verification, and any remaining remote validation.
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.
- 2d ago First seen · 27 lines · 85 tokens per session scan A 05822ea41765
ci-debugger is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 4d ago), licensed MIT. It adds 85 tokens to every session and 331 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-09-05.
Other skills, from other repositories
ci-self-heal
A diagnostic guide for analysing failed continuous-integration checks. Continuous integration, or CI, automatically tests and builds code changes; this guide classifies failures and suggests fixes without editing the code.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Use the GitHub app from this plugin for PR metadata and patch context, and use gh for Actions check and log inspection before implementing any approved fix.
termcanvas-agent-sync-debugging
Diagnose TermCanvas agentmux nodes that fail to appear and terminal canvases that become janky, resize repeatedly, or show corrupted/unreadable xterm text as terminal count grows, plus duplicate terminal views created after a release relaunch. Use when a child agent is missing, restored terminals duplicate or move to…
Debug (reproduce -> isolate -> fix)
Systematically diagnose and fix a bug instead of guessing.
incident-rca
A diagnostic process for producing a structured root-cause analysis of a serious production incident, such as a P0 or P1 outage. It compares logs, measurements, request traces, code changes, and architecture decisions, and gives ranked explanations and actions.
bug-fix
A structured bug-fixing workflow that takes a problem from reproduction and evidence-based cause finding through approval, implementation, testing, and cleanup.