Borrowing it
Nothing to install: this file belongs to Mofesto/fubon-api-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Mofesto/fubon-api-mcp-server/main/.github/skills/github-actions-debugging/SKILL.mdgit clone --depth 1 https://github.com/Mofesto/fubon-api-mcp-serverWrote 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/mofesto/fubon-api-mcp-server/github-actions-debugging)<a href="https://agentmods.dev/skills/mofesto/fubon-api-mcp-server/github-actions-debugging"><img src="https://agentmods.dev/badge/skills/mofesto/fubon-api-mcp-server/github-actions-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/mofesto/fubon-api-mcp-server/github-actions-debugging"><img src="https://agentmods.dev/badge/skills/mofesto/fubon-api-mcp-server/github-actions-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.00026 | $0.00228 |
| Opus 5.5 | $0.00010 | $0.00091 |
| Sonnet 5.5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
github-actions-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.
What it actually says
GitHub Actions Debugging
This skill helps you debug failing GitHub Actions workflows in pull requests.
Process
- Use the
list_workflow_runstool to look up recent workflow runs for the pull request and their status - Use the
summarize_job_log_failurestool to get an AI summary of the logs for failed jobs - If you need more information, use the
get_job_logsorget_workflow_run_logstool to get the full failure logs - Try to reproduce the failure locally in your environment
- Fix the failing build and verify the fix before committing changes
Common issues
- Missing environment variables: Check that all required secrets are configured
- Version mismatches: Verify action versions and dependencies are compatible
- Permission issues: Ensure the workflow has the necessary permissions
- Timeout issues: Consider splitting long-running jobs or increasing timeout values
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 · 24 lines · 26 tokens per session scan A 6e832f98e6f0
github-actions-debugging is a skill published in the GitHub repository Mofesto/fubon-api-mcp-server (17 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 228 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-08-30.
Other skills, from other repositories
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.