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/opendatahub-io/ai-helpers/github-actions-debuggernpx skills add opendatahub-io/ai-helpers --skill github-actions-debuggergit clone --depth 1 https://github.com/opendatahub-io/ai-helpersWrote 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/opendatahub-io/ai-helpers/github-actions-debugger)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/github-actions-debugger"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/github-actions-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 | $0.00056 | $0.01247 |
| Opus 5 | $0.00028 | $0.00624 |
| Sonnet 5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
github-actions-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 5d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Debugger
This skill enables Claude to investigate GitHub Actions failures by:
- Listing recent workflow runs and their status
- Identifying failed jobs within a run
- Retrieving failed job logs
- Analyzing error messages and suggesting next debugging steps
Prerequisites
ghCLI installed and authenticated (gh auth statusto verify)- Git repository with a GitHub remote configured (for automatic repo detection)
If gh is not installed, ask the user to follow installation instructions at https://cli.github.com/
If gh is not authenticated, ask the user to run gh auth login.
Instructions
When the user asks to check CI status, debug workflow failures, or view job logs, use the gh CLI commands below.
All commands auto-detect the GitHub repository from the git remote in the current working directory.
To target a different repository, add -R <owner>/<repo> to any command.
Handling GitHub Actions URLs
When the user provides a full GitHub Actions URL, parse it to extract the repository and run or job ID,
then use -R to target that repository. Always use the repository from the URL, ignoring the local git remote.
Before constructing any command from a URL, validate the extracted values:
-
Owner names must only contain letters, digits, and hyphens.
-
Repository names must only contain letters, digits, hyphens, underscores, and dots.
-
Run IDs and job IDs must be purely numeric.
-
Workflow file names must only contain letters, digits, hyphens, underscores, and dots. If any extracted value fails its rule, reject it and ask the user to provide a corrected URL or ID.
-
Run URL format:
https://github.com/<owner>/<repo>/actions/runs/<run-id>- Extract:
-R <owner>/<repo>and<run-id> - Example:
https://github.com/my-org/my-project/actions/runs/123456789becomesgh run view 123456789 -R my-org/my-project
- Extract:
-
Workflow URL format:
https://github.com/<owner>/<repo>/actions/workflows/<workflow-file>- Extract:
-R <owner>/<repo>and--workflow <workflow-file> - Example:
https://github.com/my-org/my-project/actions/workflows/ci.yamlbecomesgh run list --workflow ci.yaml -R my-org/my-project
- Extract:
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.
- 5d ago First seen · 122 lines · 56 tokens per session scan A 4cb73ba812ad
github-actions-debugger is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 1,247 once invoked, about $0.0003 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
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
secrets-management
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.