gitlab-api-operations

A governed operating guide for using GitLab through connected tools. GitLab is a service for hosting code, tracking work, reviewing changes, and running software checks.

In plain words
What is it for?
Use it for GitLab issue work, merge requests, pipeline checks, security findings, data ingestion, troubleshooting, and related evidence workflows.
Why use it?
It adds a controlled process for discovering available operations, previewing changes, protecting credentials, and verifying results. This lowers the risk of unintended or untraceable GitLab changes.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/knuckles-team/gitlab-api/gitlab-api-operations
Any agent
npx skills add Knuckles-Team/gitlab-api --skill gitlab-api-operations
Clone the repo
git clone --depth 1 https://github.com/Knuckles-Team/gitlab-api

Made for: Claude Code, Codex.

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 330 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.00330
Opus 5 $0.00033 $0.00165
Sonnet 5 $0.00013 $0.00066
Haiku 4.5 $0.00007 $0.00033

Measured yesterday against content hash 779c2f12e4fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitlab-api-operations 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 yesterday.

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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

gitlab_api/skills/gitlab-api-operations/SKILL.md · 34 lines

What it actually says

Gitlab Api Operations

Use the provider's governed MCP tools through GraphOS delegation.

Workflow

  1. Establish the verified GraphSession and tenant before discovery or retrieval.
  2. Discover the current condensed tool surface; never assume a stale tool name or schema.
  3. Prefer read-only inspection first. For changes, present impact and use the provider's dry-run or preview mode when available.
  4. Execute mutations as fenced WorkItems so retries remain idempotent and auditable.
  5. Ingest source data only through the signed connector preset and ChangeEnvelope path.
  6. Verify the durable result and its trace/evidence before reporting completion.

Safety contract

  • Never persist credentials, endpoints, raw personal identifiers, hostnames, or local paths.
  • Resolve TLS trust and verification from environment/configuration; never hardcode bypasses.
  • Treat unknown ACL, tenant, schema, or tool-contract state as a hard failure.
  • Require explicit approval for destructive, externally visible, or irreversible actions.
  • Keep runtime traces policy-scoped and privacy-sanitized.

Specialized workflows

Read the workflow catalog only when the request needs a provider-specific procedure, parameter map, script, or reference asset.

Files

What ships with it

2 files 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.

Changes

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.

  1. yesterday First seen · 34 lines · 66 tokens per session scan A 779c2f12e4fd

Subscribe to this mod's changes

gitlab-api-operations is a skill published in the GitHub repository Knuckles-Team/gitlab-api (10 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 330 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-31.