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/automateyournetwork/netclaw/gitlab-devopsnpx skills add automateyournetwork/netclaw --skill gitlab-devopsgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/gitlab-devops)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/gitlab-devops"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/gitlab-devops.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00067 | $0.03854 |
| Opus 5 | $0.00034 | $0.01927 |
| Sonnet 5 | $0.00013 | $0.00771 |
| Haiku 4.5 | $0.00007 | $0.00385 |
Grade A, and why
gitlab-devops 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.
How it starts
The opening of the file, as written. The whole thing — 582 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab DevOps Skill
Golden Rule
Never execute write operations (create, update, delete, merge) without explicit operator confirmation. All mutating actions — creating issues, merging MRs, triggering pipelines, deleting labels — require human-in-the-loop approval before invocation (Constitution XIV). Always observe current state before making changes (Constitution II: Read-Before-Write).
MCP Server
This skill uses tools provided by the gitlab-mcp server (@zereight/mcp-gitlab), a community MCP server with 98+ tools for GitLab operations. The server is spawned locally via npx -y @zereight/mcp-gitlab and communicates over stdio transport.
Environment Variables
| Variable | Required | Description |
|---|---|---|
GITLAB_PERSONAL_ACCESS_TOKEN |
Yes | GitLab PAT with api or read_api scope |
GITLAB_API_URL |
No | GitLab API URL (default: https://gitlab.com) |
GITLAB_READ_ONLY_MODE |
No | Restrict to read-only tools (default: false) |
Workflow 1: Query Issues and Merge Requests (P1 — MVP)
Use this workflow to search, list, and inspect GitLab issues and merge requests for network project tracking.
Step 1: Discover Projects
Find the target project by name or keyword:
Tool: search_projects
Parameters: { "query": "network-automation" }
Or list all accessible projects:
Tool: list_projects
Parameters: { "per_page": 20 }
Step 2: List Issues
Query issues with filters for state, labels, assignee, or milestone:
Tool: list_issues
Parameters: {
"project_id": "network-team/network-automation",
"state": "opened",
"labels": "outage",
"assignee_username": "jcapobianco"
}
Step 3: Get Issue Details
Retrieve full details for a specific issue:
Tool: get_issue
Parameters: {
"project_id": "network-team/network-automation",
"issue_iid": 42
}
Step 4: View Issue Comments
List the discussion thread on an issue:
Tool: list_issue_comments
Parameters: {
"project_id": "network-team/network-automation",
"issue_iid": 42
}
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.
- yesterday First seen · 582 lines · 67 tokens per session scan A 78b28a37453e
gitlab-devops is a skill published in the GitHub repository automateyournetwork/netclaw (650 stars, last pushed yesterday), licensed Apache-2.0. It adds 67 tokens to every session and 3,854 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-09-03.
Other skills, from other repositories
pace-release
Use when user says "发布", "部署", "上线", "release", "pace-release", or wants to create, deploy, or close a release. NOT for CI/CD pipeline management (use /pace-sync). NOT for code implementation (use /pace-dev).
repo-recap
Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass "en" or "fr" as argument for language (default fr).
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
maintainer-release-ops
Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, assess milestone health, coordinate release blockers, or generate a release-focused review brief.