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 opendatahub-io/ai-helpers --skill gitlab-pipeline-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/gitlab-pipeline-debugger)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/gitlab-pipeline-debugger"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/gitlab-pipeline-debugger/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/opendatahub-io/ai-helpers/gitlab-pipeline-debugger"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/gitlab-pipeline-debugger.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.00056 | $0.01087 |
| Opus 5 | $0.00028 | $0.00544 |
| Sonnet 5 | $0.00011 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
gitlab-pipeline-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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab CI Debugger
This skill enables Claude to investigate GitLab CI pipeline failures by:
- Checking the current pipeline status for a branch or a specific pipeline ID
- Identifying failed jobs
- Retrieving failed job logs
- Analyzing error messages and suggesting fixes
Prerequisites
glabCLI installed and authenticated (glab auth statusto verify)- Git repository with GitLab remote configured (for automatic repo detection)
If glab is not installed, ask the user to follow installation instructions at https://gitlab.com/gitlab-org/cli#installation
If glab is not authenticated, ask the user to run glab auth login.
Instructions
When the user asks to check CI status, debug pipeline failures, or view job logs, use the glab CLI commands below.
All commands auto-detect the GitLab project from the git remote in the current working directory.
To target a different project, add -R <owner/group/project> to any command.
Handling GitLab URLs
When the user provides a full GitLab URL, parse it to extract the project path and the pipeline or job ID,
then use -R to target that project. Always use the project from the URL, ignoring the local git remote.
Before constructing any command from a URL, validate the extracted values:
-
Project paths must only contain letters, digits, hyphens, underscores, dots, and forward slashes.
-
Pipeline and job IDs must be purely numeric.
-
Job names must only contain letters, digits, hyphens, underscores, dots, colons, slashes, and spaces. If any value fails validation, reject it and ask the user to provide a corrected URL or ID.
-
Pipeline URL format:
https://gitlab.com/<group>/<project>/-/pipelines/<pipeline-id>- Extract:
-R <group>/<project>and-p <pipeline-id> - Example:
https://gitlab.com/my-org/my-project/-/pipelines/123456becomesglab ci get -p 123456 -d -R my-org/my-project
- Extract:
-
Job URL format:
https://gitlab.com/<group>/<project>/-/jobs/<job-id>- Extract:
-R <group>/<project>and<job-id> - Example:
https://gitlab.com/my-org/my-project/-/jobs/789012becomesglab ci trace 789012 -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.
- 10d ago First seen · 103 lines · 56 tokens per session scan A 95a9fa612d45
gitlab-pipeline-debugger is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 3d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,087 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
debugging-strategies
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
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.
sql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.