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 Arvo-AI/aurora --skill gitlabgit clone --depth 1 https://github.com/Arvo-AI/auroraWrote 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/arvo-ai/aurora/gitlab)<a href="https://agentmods.dev/skills/arvo-ai/aurora/gitlab"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/gitlab/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/arvo-ai/aurora/gitlab"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/gitlab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 24 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.
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.00025 | $0.00803 |
| Opus 5.5 | $0.00010 | $0.00321 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 83 lines · 25 tokens per session scan A 98e637910ea9
gitlab is a skill published in the GitHub repository Arvo-AI/aurora (436 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 803 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
tax-lawyer-software-interfaces
MCP tool design patterns for the Tax-Lawyer Platform. Thin Satisfies wrappers (<=10 lines per handler), TaxArgs contract types, and the full tool name taxonomy for ledgerrtax MCP actions.
b00t
Identify integration points, data flow via redis, suggest how to bridge VSCode plugin to b00t jobs, and outline k0s/podman/docker-agnostic redis interface. Include how ralph should be wrapped as b00t job with redis exchange + Azure access, and call out where integration tests are required. ONLY do this analysis. Reply…
ak-add-integration
Add a messaging platform integration to an existing Agent Kernel project. This skill guides you through adding Slack, WhatsApp, Messenger, Instagram, Telegram, Teams, or Gmail integration by generating configuration, updating dependencies, and setting up webhook handlers. Designed for users extending their agents.
analytics-opensearch-expertise
Amazon OpenSearch Service domain health assessment. Performs read-only, API-driven checks against a customer's OpenSearch domain(s) covering cluster health, node/shard configuration, performance metrics, security posture, and cost optimization signals. Activate this skill for requests about OpenSearch or Elasticsearch…
database-rds-devops
Database-level data-plane diagnostics for Aurora MySQL and Aurora PostgreSQL. Executes predefined read-only health check queries via RDS Data API to analyze buffer pool, connections, locks, replication, storage, performance, and index efficiency. Requires the rds-aidba MCP server for database-internal access beyond…
storage-s3-resiliency-expertise
S3 resiliency, security, and data protection review. Assesses one or many S3 buckets across nine dimensions — versioning, replication, object lock, encryption, block public access, bucket policy, ownership controls, server access logging, and static website hosting — using read-only control-plane API calls, then…