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 PramodDutta/qaskills --skill gh-fix-cigit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/gh-fix-ci)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/gh-fix-ci"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/gh-fix-ci/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/pramoddutta/qaskills/gh-fix-ci"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/gh-fix-ci.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.00037 | $0.00699 |
| Opus 5.5 | $0.00015 | $0.00280 |
| Sonnet 5.5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
GitHub CI Fix 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CI Fix Debugging
Use gh CLI to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure, propose a fix plan, and implement after explicit approval.
Prerequisites
Authenticate with the GitHub CLI:
gh auth login # Ensure repo + workflow scopes
gh auth status # Verify authentication
Workflow
1. Verify Authentication
gh auth status
If unauthenticated, ask the user to run gh auth login with repo + workflow scopes.
2. Resolve the PR
# Current branch PR
gh pr view --json number,url
# Or use a specific PR number
gh pr checks <pr-number>
3. Inspect Failing Checks
# List all PR checks with status
gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow
# For each failing check, get the run details
gh run view <run_id> --json name,workflowName,conclusion,status,url
# Fetch the logs
gh run view <run_id> --log
4. Scope Non-GitHub Actions Checks
- If
detailsUrlis not a GitHub Actions run, label it as external - Only report the URL for external providers (Buildkite, etc.)
5. Summarize Failures
For each failing check, provide:
- The failing check name
- The run URL
- A concise log snippet showing the actual failure
- Root cause analysis
6. Create a Fix Plan
Draft a concise plan including:
- What failed and why
- Proposed fix with specific file changes
- Impact assessment
- Request explicit approval before implementing
7. Implement After Approval
- Apply the approved plan
- Summarize diffs and changes made
- Run relevant tests locally if possible
8. Recheck Status
# After fixes, verify checks pass
gh pr checks <pr>
Common CI Failure Patterns
Test Failures
- Check test output for assertion errors
- Look for environment-specific issues
- Verify test data and fixtures
Build Failures
- Check dependency versions and lockfiles
- Verify TypeScript/compilation errors
- Check for missing environment variables
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 · 116 lines · 37 tokens per session scan A 356c69f7434e
GitHub CI Fix Debugging is a skill published in the GitHub repository PramodDutta/qaskills (240 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 699 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
fixing
Diagnose why a PR's CI failed — compare the CI definition against the sandbox, classify the failure, and make the minimal repair. Use when a PR is red and you must work out why before changing anything.
ci-status-checker
Interprets GitHub Actions run status and logs, diagnoses CI failure patterns, and suggests targeted fixes. Handles dependency install failures, test timeouts, build OOM, flaky tests, and workflow misconfigurations. Activate on: 'CI failing', 'build broken', 'workflow error', 'GitHub Actions debug', 'flaky CI'…
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
ai-bug-triage
Hybrid fingerprint + LLM pipeline for bug classification, deduplication, and ticket generation. Normalizes CI logs, creates stable fingerprints, clusters near-duplicates, then uses LLM for severity classification and ticket writing. Includes bug reporting templates and severity/priority matrix. Use when: "bug triage,"…
bug-reproduction
Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end. Covers extracting the implicit repro from a thin report (env, build, steps, data), the reproduce-minimize-isolate-capture loop, git bisect to find the introducing commit, building a deterministic…
quality-postmortem
Analyze escaped defects and test suite health through blameless postmortems. Covers bug pattern analysis, test suite health reviews, 5 Whys root cause analysis, process improvement cycles, and postmortem/retro meeting templates with action item tracking. Use when: "QA retro," "escaped bugs," "postmortem," "quality…