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 cyrusagents/cyrus --skill cyrus-setup-gitlabgit clone --depth 1 https://github.com/cyrusagents/cyrusWrote 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/cyrusagents/cyrus/cyrus-setup-gitlab)<a href="https://agentmods.dev/skills/cyrusagents/cyrus/cyrus-setup-gitlab"><img src="https://agentmods.dev/badge/skills/cyrusagents/cyrus/cyrus-setup-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/cyrusagents/cyrus/cyrus-setup-gitlab"><img src="https://agentmods.dev/badge/skills/cyrusagents/cyrus/cyrus-setup-gitlab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00027 | $0.00467 |
| Opus 5.5 | $0.00011 | $0.00187 |
| Sonnet 5.5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
cyrus-setup-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.
What it actually says
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:
glab auth status 2>&1
If authenticated, check git config:
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:
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:
glab auth login --hostname gitlab.example.com
After completion, verify:
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:
git config --global user.name "<name>"
git config --global user.email "<email>"
Step 4: Verify
glab auth status
git config --global user.name
git config --global user.email
Completion
✓ GitLab CLI authenticated ✓ Git identity configured:
<name><
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 · 84 lines · 27 tokens per session scan A a477f4625484
cyrus-setup-gitlab is a skill published in the GitHub repository cyrusagents/cyrus (858 stars, last pushed 5d ago), licensed Apache-2.0. It adds 27 tokens to every session and 467 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
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
code-commit
Must be invoked when the user asks to commit code, submit code, or any similar request.
code-merge
Must be invoked when the user asks to resolve merge conflicts, merge a branch, handle an MR/PR conflict, or any similar request.
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
datalad
Retrieves, versions, and publishes scientific datasets with DataLad and git-annex, and captures computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink…
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.