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 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/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/automateyournetwork/netclaw/gitlab-devops"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/gitlab-devops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 576 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.
- medium MCP Rug Pull · line 19 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00067 | $0.03854 |
| Opus 5.5 | $0.00027 | $0.01542 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 582 lines · 67 tokens per session scan A 78b28a37453e
gitlab-devops is a skill published in the GitHub repository automateyournetwork/netclaw (684 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.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
A release-management workflow for coordinating software versions from preparation through deployment and closure. A release is a planned delivery of changes to users or an environment.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
operating-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.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…