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 CodeInfinity1/Stram --skill ci-failure-debugginggit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/ci-failure-debugging)<a href="https://agentmods.dev/skills/codeinfinity1/stram/ci-failure-debugging"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/ci-failure-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/codeinfinity1/stram/ci-failure-debugging"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/ci-failure-debugging.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00565 |
| Opus 5.5 | $0.00012 | $0.00226 |
| Sonnet 5.5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
ci-failure-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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Failure Debugging
Purpose
Turn red CI into actionable evidence and a verified fix. This skill separates CI environment issues, test failures, dependency problems, and real regressions.
When To Use
Use when GitHub Actions or other CI checks fail, PR checks are red, logs need inspection, or local tests differ from CI.
Inputs And Evidence
- PR/commit, failing check name, log output, local reproduction command, and changed files.
- CI environment, dependency versions, and workflow config.
Tool Map
ci_failure_report_creategithub_artifact_inspectgithub_pr_packet_creategithub_repo_state_report_createrun_shell_commandread_filesearch_workspacesystematic-debugginggithub-pr-workflowcode-review
Workflow
- Identify failing check and current commit.
- Retrieve logs with
ghor provided evidence. - Classify failure: test, lint, build, environment, auth, flake, or workflow config.
- Create a durable
ci_failure_report_createartifact with check name, workflow/run URL, log excerpt, suspected causes, reproduction commands, fix plan, verification, and residual risks. - Inspect the report with
github_artifact_inspectbefore patching or summarizing. - Reproduce locally when feasible.
- Patch root cause, not just CI symptoms.
- Run targeted local checks and re-inspect CI status after push if requested.
Native Implementation Boundaries
- Use native shell/GitHub CLI and repo tooling.
- Use native CI failure report artifacts to hold evidence and avoid brittle log-pattern fixes.
- Do not import external CI-fix scripts.
- Do not hardcode failure-pattern-to-fix maps.
Safety And Approval
- Do not weaken tests, ignore lint, or skip CI without explicit reason.
- Pushing CI fixes requires user intent.
- Redact secrets from logs.
Verification
- A fixed claim needs passing local command or current CI evidence.
- If CI cannot be checked, report local-only verification.
- Local CI reports should show
live_execution_status: not_executedwhen no live CI query or update occurred. - Keep residual flake risk explicit.
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 · 75 lines · 29 tokens per session scan A 83aed3e842da
ci-failure-debugging is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 565 once invoked, about $0.0001 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-03.
Other skills, from other repositories
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
verification-quality
Truth scoring, code-quality verification, and automatic rollback with a high accuracy threshold. Use when validating agent output before it ships, gating changes on quality, or adding a verify-and-rollback safety loop.
test-e2e
End-to-end infrastructure pipeline validation across Terraform and Ansible repos.
ci-test-optimization
A guide for analysing and preparing improvements to a CI test pipeline. CI, or continuous integration, automatically builds and tests code changes as they are submitted.
everr-use-telemetry
Use when investigating production or local behavior with logs, traces, metrics, errors, crashes, slow requests, flaky tests, regressions, missing behavior, stale telemetry, user reports, incidents, or questions that real runtime data can answer.
everr-working-with-ci
Use when a task mentions CI, GitHub Actions, workflow runs, checks, jobs, steps, logs, build or test failures, flaky or slow CI, PR status, branch status, release pipelines, or whether a commit is green.