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 Knuckles-Team/gitlab-api --skill gitlab-pipelinesgit clone --depth 1 https://github.com/Knuckles-Team/gitlab-apiWrote 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/knuckles-team/gitlab-api/gitlab-pipelines)<a href="https://agentmods.dev/skills/knuckles-team/gitlab-api/gitlab-pipelines"><img src="https://agentmods.dev/badge/skills/knuckles-team/gitlab-api/gitlab-pipelines/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/knuckles-team/gitlab-api/gitlab-pipelines"><img src="https://agentmods.dev/badge/skills/knuckles-team/gitlab-api/gitlab-pipelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 41 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00130 | $0.01186 |
| Opus 5.5 | $0.00052 | $0.00474 |
| Sonnet 5.5 | $0.00026 | $0.00237 |
| Haiku 4.5 | $0.00013 | $0.00119 |
Grade A, and why
gitlab-pipelines 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Pipelines
Domain-typed review of GitLab CI/CD Pipelines — pipeline results at project, group, or instance scope, the jobs within a pipeline, and per-job logs. Also triggers a pipeline on a ref.
When to use
- Review pipeline results for a project / ref (is
maingreen?). - Review CI results across a group / organization (enumerate projects, then their pipelines).
- Fetch a single pipeline by
pipeline_id, list its jobs, and read a job log. - Trigger (
run) a new pipeline on a branch or tag.
When NOT to use
- Gating one MR's merge on its pipeline →
gitlab-merge-request-review(it reads the MR's pipeline/jobs/logs directly). - Issues, epics, milestones →
gitlab-issues. - Branch/commit/tag/project reads →
gitlab-repositories.
Prerequisites & environment
Connect via the mcp-client skill against the gitlab-api MCP server.
| Variable | Required | Notes |
|---|---|---|
GITLAB_URL |
✅ | GitLab instance base URL |
GITLAB_TOKEN |
✅ | Access token with api scope (needed to run) |
GITLAB_SSL_VERIFY |
optional | TLS verification toggle |
Full env/tag matrix: the mcp-client reference agent-tools/mcp-client/references/gitlab-api.md.
MCP_TOOL_MODE (condensed|verbose|both) selects the condensed vs. one-to-one verbose tools.
Tools & actions
| Condensed tool | Actions |
|---|---|
gitlab_groups |
get_projects (enumerate a group's projects) |
gitlab_pipelines |
get, run |
gitlab_jobs |
get_pipeline_jobs, get_project_jobs, get_log, retry, cancel |
Key parameters
- Scope — project:
gitlab_pipelines getwithproject_id. group/org:gitlab_groups get_projects(group_id) thengitlab_pipelines getper project. instance: iterate the projects you care about. gitlab_pipelines get:project_id(required);pipeline_idfor a single pipeline; filtersref,status,order_by,sort,per_page.gitlab_jobs get_pipeline_jobs:project_id+pipeline_id— the jobs of one pipeline.gitlab_jobs get_log:project_id+job_id— the job trace/log.gitlab_pipelines run:project_id+ref; optionalvariablesobject.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 102 lines · 130 tokens per session scan A a299f4e216aa
gitlab-pipelines is a skill published in the GitHub repository Knuckles-Team/gitlab-api (10 stars, last pushed today), licensed MIT. It adds 130 tokens to every session and 1,186 once invoked, about $0.0005 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-31.
Other skills, from other repositories
servicenow-studio-gitlab-app
Wire a ServiceNow scoped app (App Engine Studio / Fluent) to a GitLab repository and drive its promotion two ways — Path A: native Studio source control (servicenowsourcecontrol → importrepository / applyremotesourcecontrolchanges, handing off to servicenowcicd for publish/install), or Path B: GitLab-CI-driven…
gitlab-mcp-skill
Use this skill when working with the GitLab MCP server tools for merge requests, issues, repositories, pipelines, work items, variables, dependency proxy, vulnerabilities, webhooks, search, CI catalog, and related GitLab workflows.
servicenow-cicd-devops
ServiceNow release-engineering surface — CI/CD app install/scan/rollback, DevOps change-control and artifact registration, update-set create/preview/commit/back-out, source-control apply/import, plugin activate/rollback, and ATF test-suite runs via the servicenow-api MCP server. Use when the agent must deploy or roll…
servicenow-api-operations
Operate servicenow-api through its governed MCP and GraphOS capabilities, including servicenow app engine, servicenow change management, servicenow cicd devops, servicenow cmdb, servicenow hr ppm, servicenow import attachment batch, servicenow incident management, servicenow irm grc, and related workflows. Use when a…
jellyfin-kg-ingestion
Natively ingest a Jellyfin library into the epistemic-graph knowledge graph via the jellyfin-mcp MCP server — push library items as typed :MediaAsset/:Book nodes with :hasGenre/:performedBy/:authoredBy links and item overviews as searchable :Document nodes (jellyfiningestlibrary), and item posters as content-addressed…
jellyfin-library-catalog
Browse and search a Jellyfin media library via the jellyfin-mcp MCP server — list library items (movies, series, episodes, audio, books), fetch one item by id, walk collections and user views, and run search hints with the domain-typed jellyfinlibrary tool. Use when the agent must find or enumerate catalog items…