Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fprochazka/claude-code-plugins/plugin install glabWrote 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/fprochazka/claude-code-plugins/pipeline)<a href="https://agentmods.dev/skills/fprochazka/claude-code-plugins/pipeline"><img src="https://agentmods.dev/badge/skills/fprochazka/claude-code-plugins/pipeline/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/fprochazka/claude-code-plugins/pipeline"><img src="https://agentmods.dev/badge/skills/fprochazka/claude-code-plugins/pipeline.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.00011 | $0.00513 |
| Opus 5.5 | $0.00004 | $0.00205 |
| Sonnet 5.5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
pipeline 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 25d 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
Context
${CLAUDE_PLUGIN_ROOT}/scripts/mr-state.py --pipeline
Your task
Analyze the MR pipeline state above, no implementation yet. Help triage any issues by analyzing the logs of any failed jobs and looking up the context and proposing fixes. If all jobs passed, report the pipeline status and note that no action is needed.
Reading the pipeline dump
The script already ran glab-pipeline inspect for you. Read the dump in this order and stop as soon as you have the cause:
- The pipeline summary file printed above — it names each failed job, its stage, and its failure reason, and it points at the file that explains it. Read it first, never the raw dump directory.
job-logs/<failed-job>.logfor a script or runtime failure — the tail carries the error. Read only the logs the summary names. Do not read the logs of jobs that passed.test-report.jsonfor a test failure — it holds per-test results, which beats grepping a long trace.lint.jsonandmerged.ymlfor a YAML,needs, or config error — they show what GitLab actually parsed.downstream/<bridge>-<id>.jsonfor a failed child pipeline, then recurse withglab-pipeline inspect --pipeline-id <id>.
summary.json in the same directory holds the same summary as structured data. Use it when you want to filter with jq instead of reading prose.
Running glab-pipeline yourself
Invoke the glab-pipeline skill before you run the CLI directly. Run it again when the dump is stale or incomplete:
- After a retry or a new push, to inspect the new pipeline.
- With
--with-merged-ci-configwhen aninclude:resolves differently on the source branch. - With
--with-test-reportwhen a test job failed but the report is missing.
Use glab ci retry <job-name> to retry a job. glab-pipeline inspects only, so it has no retry of its own.
Additional instructions
$ARGUMENTS
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.
- 25d ago Changed · +2 lines 21bc7a931d60
- 1mo ago First seen · 42 lines · 11 tokens per session scan A 4281aeab0fee
pipeline is a skill published in the GitHub repository fprochazka/claude-code-plugins (15 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 513 once invoked, about $0.0000 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-12.
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.