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/arvo-ai/aurora/gitlabnpx skills add Arvo-AI/aurora --skill gitlabgit clone --depth 1 https://github.com/Arvo-AI/auroraWhat 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.00025 | $0.00803 |
| Opus 5 | $0.00013 | $0.00402 |
| Sonnet 5 | $0.00005 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00080 |
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Integration
Overview
GitLab integration for investigating code changes during Root Cause Analysis and managing code fixes. Connected via org-level Group Access Token. Instance: {base_url}
Instructions
Single Tool — Multiple Actions
All GitLab operations use the gitlab tool with an action parameter:
| Action | Purpose | Required Params |
|---|---|---|
list_projects |
Discover connected projects | — |
deployment_check |
CI/CD pipelines | repo (or auto) |
commits |
Recent commits + correlation | repo (or auto) |
diff |
File changes for a commit | commit_sha |
merge_requests |
Merged MRs in time window | repo (or auto) |
suggest_fix |
Propose a code fix | file_path, suggested_content, fix_description, root_cause_summary |
apply_fix |
Create MR from suggestion | suggestion_id |
commit_terraform |
Push Terraform files | repo, commit_message |
RCA Investigation Workflow
Code changes are the most common root cause of incidents. Investigate GitLab BEFORE deep-diving into infrastructure.
Step 1 — Discover projects:
gitlab(action='list_projects') — returns all connected projects.
Step 2 — Check pipelines (did something just ship?):
gitlab(action='deployment_check', repo='namespace/project', incident_time='<ISO8601>')
Finds failed pipelines and pipelines completed within 2 hours of the incident.
Step 3 — Check commits (what code changed?):
gitlab(action='commits', repo='namespace/project', incident_time='<ISO8601>')
Lists commits with automatic suspicious-commit flagging.
Step 4 — Inspect suspicious changes:
gitlab(action='diff', repo='namespace/project', commit_sha='<sha>')
Shows file-level additions/deletions. Prioritize config/infra files.
Step 5 — Check merged MRs:
gitlab(action='merge_requests', repo='namespace/project', incident_time='<ISO8601>')
Finds MRs merged in the time window; recently merged MRs are flagged.
Post-RCA Remediation (after user approval)
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 · 83 lines · 25 tokens per session scan A 98e637910ea9
gitlab is a skill published in the GitHub repository Arvo-AI/aurora (401 stars, last pushed 4d ago), licensed Apache-2.0. It adds 25 tokens to every session and 803 once invoked, about $0.0001 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
cloud-iam-deep
GCP/AWS/Azure cloud exploitation -- Cloud Functions, Firestore, Cloud Run, S3, MinIO, Blob Storage, SA keys.
awesome-kubernetes-ops
This skill documents the local verification, editing, and deployment procedures for the Antigravity AI Agent when pair-programming with the repository maintainer.
isaac-automator
Deploy and operate a cloud Isaac Workstation with Isaac Automator: provision a GPU VM running Isaac Sim, Isaac Lab, and/or Isaac Lab Arena on AWS, GCP, Azure, or Alibaba Cloud, connect to it, move data in and out, control cost with stop/start, repair, import existing deployments, and destroy. Use when the user wants a…
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
console-audit
Audit the running app via chrome-devtools MCP — console errors/warnings + failed/slow network by default; perf (LCP/CLS) and Lighthouse (a11y/SEO) are opt-in. Token-efficient (compacts findings in-browser via a console/network hook); the report is shown inline in the response — no files to open. Target one tab / an…
create-issue
Create GitHub issues using repo templates (feature, bug, spike).