Cyrus Setup GitlabCAUTION
The Claude Code background agent for Linear, Slack, Github, GitLab etc. you deploy anywhere. Supports Codex, Cursor, Gemini, and Opencode harnesses too.
Overview
The Claude Code background agent for Linear, Slack, Github, GitLab etc. you deploy anywhere. Supports Codex, Cursor, Gemini, and Opencode harnesses too.
a792ab0e17bbOBSERVED · 2026-10-13What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: cyrus-setup-gitlab description: Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests. --- **CRITICAL: Never use `Read`, `Edit`, or `Write` tools on `~/.cyrus/.env` or any file inside `~/.cyrus/`. Use only `Bash` commands (`grep`, `printf >>`, etc.) to interact with env files — secrets must never be read into the conversation context.** # Setup GitLab Configures GitLab CLI and git so Cyrus can create branches, commits, and merge requests. ## Step 1: Check Existing Configuration Check if `glab` is already authenticated: ```bash glab auth status 2>&1 ``` If authenticated, check git config: ```bash git config --global user.name git config --global user.email ``` If both `glab` auth and git config are set, inform the user: > GitLab is already configured. Skipping this step. Skip to completion. ## Step 2: Authenticate GitLab CLI If `glab` is not authenticated: ```bash glab auth login ``` This opens an interactive browser flow. Let the user complete it. For self-hosted GitLab instances, the user can specify the hostname: ```bash glab auth login --hostname gitlab.example.com ``` After completion, verify: ```bash glab auth status ``` ## Step 3: Configure Git Identity If git user name or email are not set, ask the user for their preferred values: > **What name should appear on commits made by Cyrus?** > (e.g., your name, or "Cyrus Bot") > **What email should appear on commits?** > (e.g., your email, or a noreply address) Then set them: ```bash git config --global user.name "<name>" git config --global user.email "<email>" ``` ## Step 4: Verify ```bash glab auth status git config --global user.name git config --global user.email ``` ## Completion > ✓ GitLab CLI authenticated > ✓ Git identity configured: `<name>` <`email`>
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (5)
.claude/skills/cyrus-setup
.claude/skills/cyrus-setup-claude-auth
.claude/skills/cyrus-setup-endpoint
.claude/skills/cyrus-setup-github
.claude/skills/cyrus-setup-gitlab
Gates applied: no_behavioural_pass.
a792ab0e17bbfull audit observations/trust-audit/skill/cyrusagents__cyrus-setup-gitlab.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-13 | a792ab0e17bb | CAUTION | B | 89 | first audit |
Questions
What does the Cyrus Setup Gitlab skill do?
The Claude Code background agent for Linear, Slack, Github, GitLab etc. you deploy anywhere. Supports Codex, Cursor, Gemini, and Opencode harnesses too.
Is Cyrus Setup Gitlab safe to install?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Cyrus Setup Gitlab access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (a792ab0e17bb), read on 2026-10-13. The repository is watched, and a new audit runs when it changes — this is the first audit.