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 agentmods add skills/neverinfamous/memory-journal-mcp/gitlabnpx skills add neverinfamous/memory-journal-mcp --skill gitlabgit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWhat 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 | $0.00106 | $0.00889 |
| Opus 5 | $0.00053 | $0.00445 |
| Sonnet 5 | $0.00021 | $0.00178 |
| Haiku 4.5 | $0.00011 | $0.00089 |
Grade A, and why
gitlab 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 2d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Skill
You are a specialized assistant for managing repositories and CI/CD in GitLab. This skill enables querying projects, merge requests, pipelines, and searching code.
Prerequisites
Before using this skill, ensure:
- The
GITLAB_API_TOKENis available in the environment. Prefer using OS credential stores or the active workspace's.envfile rather than hardcoded global paths. - A recent version of Bun/Node is installed.
- Network access to the GitLab instance.
Skill Structure
skills/gitlab/
├── SKILL.md # This file
├── package.json # TS dependencies (@gitbeaker/rest)
└── scripts/
├── gitlab-client.ts # Core GitLab REST API client
└── gitlab-helper.ts # High-level repository operations
Quick Start
You can use the helper script via a quick TS sandbox, utilizing bun if available, or straight Node via tsx.
import { GitLabHelper } from './skills/gitlab/scripts/gitlab-helper.js'
const helper = new GitLabHelper()
// Verify connection
const user = await helper.connect()
// List projects
const projects = await helper.listProjects({ membership: true })
// Get a specific project
const project = await helper.getProject('group/project-name')
// List open merge requests
const mrs = await helper.listMergeRequests('group/project', 'opened')
// List pipelines
const pipelines = await helper.listPipelines('group/project', 'success')
Common Tasks
1. Check Pipeline Status
const pipeline = await helper.getLatestPipeline('group/project', 'main')
console.log(`Pipeline #${pipeline.id}: ${pipeline.status}`)
if (pipeline.status === 'failed') {
const jobs = await helper.getPipelineJobs('group/project', pipeline.id)
for (const job of jobs) {
if (job.status === 'failed') {
const log = await helper.getJobLog('group/project', job.id)
console.log(log.substring(log.length - 1000))
}
}
}
2. Review Merge Requests
const mrs = await helper.getAssignedMergeRequests()
for (const mr of mrs) {
console.log(`!${mr.iid}: ${mr.title}`)
console.log(` ${mr.source_branch} -> ${mr.target_branch}`)
console.log(` Author: ${mr.author.username}`)
}
What ships with it
4 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.
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.
- 2d ago First seen · 121 lines · 106 tokens per session scan A 44c99e9d32ba
gitlab is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 106 tokens to every session and 889 once invoked, about $0.0005 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
ci-failure-investigator
Route CI run, job, and Allure failure investigations to the canonical playbook.
recreate-dependabot-pr
Recreate stale Dependabot PR(s) for keboola/mcp-server as a fresh branch from main, producing a clean, conflict-free PR. This repo manages Python deps via uv (pyproject.toml + uv.lock) and GitHub Actions, so updates are applied with uv lock --upgrade-package and workflow edits — not composer. Use when Dependabot PRs…
mykg-github-pages
Set up and maintain the GitHub Pages site for the mykg repo (SenolIsci/mykg) — a purpose-built pages/ folder (landing page adapted from README.md, blog posts, diagrams), built by a GitHub Actions workflow that runs Jekyll and deploys the result to a gh-pages branch. Use whenever the user wants to publish project…
gate-probe
Prove a gate before trusting it. Inventory violations, plant a defect, verify RED, restore GREEN, prevent idle scans, and confirm automatic wiring.
publishing
Publishing and release workflow with semantic-release and GitHub Actions.
council-gate
Quality gate using LLM Council multi-model consensus for CI/CD pipelines. Use for automated approval workflows and pipeline quality checks. Keywords: gate, CI, CD, pipeline, automated approval, quality gate, GitHub Actions.