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 dayfinggg/openai-codex-agent-skills --skill ci-failure-diagnosisgit clone --depth 1 https://github.com/dayfinggg/openai-codex-agent-skillsWrote 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/dayfinggg/openai-codex-agent-skills/ci-failure-diagnosis)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/ci-failure-diagnosis"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/ci-failure-diagnosis/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/dayfinggg/openai-codex-agent-skills/ci-failure-diagnosis"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/ci-failure-diagnosis.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.00041 | $0.00362 |
| Opus 5.5 | $0.00016 | $0.00145 |
| Sonnet 5.5 | $0.00008 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
ci-failure-diagnosis 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 today.
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
Repair the first causal CI failure without weakening the pipeline.
- Establish the provider, repository, commit, workflow or pipeline, failed jobs, and relevant attempt. A green run on a different commit is not verification.
- Read the failing step's complete useful output and preceding setup. Distinguish the primary failure from downstream cancellations, cleanup errors, and summarized annotations.
- Compare tool versions, lockfiles, platform, service dependencies, environment variables, permissions, working directory, and caches with local execution. Inspect only relevant configuration and redact secrets.
- Form a reproduction using the repository's existing commands and a representative environment. If reproduction is unavailable, retain that uncertainty rather than inventing a local success.
- Classify deterministic code failure, infrastructure failure, missing prerequisite, timing dependence, or flaky test using evidence. A single successful rerun does not explain a flake.
- Make the smallest cause-directed correction. Do not skip tests, lower analysis, remove supported events, refresh snapshots blindly, or replace a failing assertion with a weaker one.
- Run targeted verification, then the affected CI path for the corrected commit where authorized. Use the host's event or PR-watching tools when completion waits on remote checks. Do not start polling loops.
Preserve logs needed for an active investigation and remove task-owned disposable fixtures once no longer needed. Finish with the cause, scoped correction, actual verified commit, and any remaining failed check.
When provider configuration changes are required, use an applicable installed workflow skill or the provider's official documentation for the deployed version.
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.
- today First seen · 20 lines · 41 tokens per session scan A 2a20b3a73999
ci-failure-diagnosis is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (8 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 362 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-10-30.
Other skills, from other repositories
diagnose-ci
Investigate failing REMOTE CI runs on GitHub Actions: find the failed run, pull the failed-step logs with gh, identify the root cause (compile error, test failure, lint, missing secret, timeout), and recommend a fix. Read-only: it does not commit, push, or edit. Use when CI is red, a GitHub Actions run failed, or the…
ci-debug-loop
Watch a GitHub Actions CI run, diagnose failures from logs, apply fixes, re-push, and repeat until green or escalate. Use when CI is failing and the user wants to debug and fix it iteratively, or says "fix CI", "debug the build", or similar.
full-review
Full review or routine upkeep: read every repo area, fix tools, dead code, stale config, and ignore files, and prove all checks pass.
fix-and-retry
Diagnose a failing CI run, apply the code fix, commit it, push, and watch the re-run until it passes or fails -- the full fix-and-retry loop in one shot. Use after a pipeline fails and the user says "fix it and retry", "fix the CI and push", or "make CI green". Do NOT use for a read-only investigation that stops at a…
verification-and-release
Design risk-based verification and judge release readiness from traceable evidence. Use when deciding what must be proven or whether an integrated change can ship.
gh-actions-failure-triage
Inspect failing GitHub Actions checks, isolate the actionable failure, and turn it into a concrete fix path with verification steps.