gitlab-wiki

gitlab-wiki is a skill for Claude Code from grandcamel/GitLab-Assistant-Skills. It costs 51 tokens per session (2,306 once invoked), scanned A, original, MIT.

A set of commands for managing GitLab wiki pages, which are project documentation pages stored in GitLab.

In plain words
What is it for?
Use it to list, read, create, update, and delete wiki pages, and to upload files used by those pages.
Why use it?
It lets you maintain project documentation and attachments from the same command-line workflow as other GitLab tasks.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the gitlab-assistant-skills plugin — 19 skills, 3 commands shipped together

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/grandcamel/gitlab-assistant-skills/gitlab-wiki
Any agent
npx skills add grandcamel/GitLab-Assistant-Skills --skill gitlab-wiki
Clone the repo
git clone --depth 1 https://github.com/grandcamel/GitLab-Assistant-Skills

Made for: Claude Code.

Or install gitlab-assistant-skills, the plugin that ships this one along with the rest of its 19 skills, 3 commands.

Wrote 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.

agentmods badge for gitlab-wiki

README.md
[![agentmods](https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-wiki.svg)](https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-wiki)
Your own site
<a href="https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-wiki"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-wiki.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,306 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.1 $0.00051 $0.02306
Opus 5 $0.00026 $0.01153
Sonnet 5 $0.00010 $0.00461
Haiku 4.5 $0.00005 $0.00231

Measured 5d ago against content hash 51964e5f5e79, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

gitlab-wiki 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 5d 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.

skills/gitlab-wiki/SKILL.md · 278 lines

How it starts

The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Wiki Skill

Wiki page management for GitLab using glab api raw endpoint calls.

Quick Reference

Operation Command Pattern Risk
List pages glab api projects/:id/wikis -
Get page glab api projects/:id/wikis/:slug -
Create page glab api projects/:id/wikis -X POST -f ... ⚠️
Update page glab api projects/:id/wikis/:slug -X PUT -f ... ⚠️
Delete page glab api projects/:id/wikis/:slug -X DELETE ⚠️⚠️
Upload attachment glab api projects/:id/wikis/attachments -X POST ... ⚠️

Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger

When to Use This Skill

ALWAYS use when:

  • User mentions "wiki", "wiki page", "documentation page"
  • User wants to create/edit project documentation in GitLab
  • User mentions wiki slugs or wiki content
  • User wants to upload images to wiki

NEVER use when:

  • User wants README files (use gitlab-file)
  • User wants to search wiki content (use gitlab-search with wiki_blobs scope)
  • User wants external documentation (not GitLab wiki)

API Prerequisites

Required Token Scopes: api

Permissions:

  • Read wiki: Reporter+ (for private repos)
  • Write wiki: Developer+ (or based on project settings)

Note: Wiki must be enabled for the project.

Available Commands

List Wiki Pages

# List all wiki pages
glab api projects/123/wikis --method GET

# With pagination
glab api projects/123/wikis --paginate

# Using project path
glab api "projects/$(echo 'mygroup/myproject' | jq -Rr @uri)/wikis"

Get Wiki Page

# Get page by slug
glab api projects/123/wikis/home --method GET

# Get page with spaces in slug (URL-encode)
glab api "projects/123/wikis/$(echo 'Getting Started' | jq -Rr @uri)" --method GET

# Get nested page
glab api "projects/123/wikis/$(echo 'docs/installation' | jq -Rr @uri)" --method GET

# Get page with specific version
glab api "projects/123/wikis/home?version=abc123" --method GET

# Render HTML
glab api "projects/123/wikis/home?render_html=true" --method GET

Read the full file on GitHub · 278 lines

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. 5d ago First seen · 278 lines · 51 tokens per session scan A 51964e5f5e79

Subscribe to this mod's changes

gitlab-wiki is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 51 tokens to every session and 2,306 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.

Related

Other skills, from other repositories

code-gauntlet

Prefer this skill for code review requests — it runs a multi-agent pipeline with blind challenge verification for high-confidence results. Trigger for ANY of these situations: (1) user says "review" in the context of code, PRs, MRs, branches, diffs, or changes, (2) user references a PR/MR number and wants feedback or…

liatrio-labs/claude-code-gauntlet · 218 tokens

build-review-md

Use this skill when the user wants to create or set up a REVIEW.md configuration file for their repository. Trigger for ANY of these: (1) user says "create REVIEW.md", "set up REVIEW.md", or "configure review rules", (2) code-gauntlet Phase 2d detects no REVIEW.md and suggests creating one, (3) user wants to customize…

liatrio-labs/claude-code-gauntlet · 171 tokens

asana-sweep

Scheduled sweep of incomplete Asana tasks assigned to you — triage into auto/ask/skip, dedupe against existing work, then call asana-to-harness to open GitLab issues that trigger an AI coding harness. Built for headless scheduled runs (claude -p); also runs interactively, with --dry-run support.

YCyrus/asana-sweep · 72 tokens

asana-to-harness

Turn one Asana task into an implementation plan for an AI coding harness, open a GitLab issue with the plan as its description, and leave a trigger comment (e.g. @claude). Used standalone ("turn this Asana task into a harness issue") or invoked by the asana-sweep skill.

YCyrus/asana-sweep · 68 tokens

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

review

5-pass structured code review — correctness, security, performance, readability, consistency.

SethGammon/Citadel · 17 tokens