Agent skill · Audited from source

cyrus-setup-repository

skill · ceedaragents/cyrusApache-2.0 licenceAudited 27 Oct 2026 · source 8ac3bf1a38f4

★ 875pushed today
!CAUTIONGrade B · 89/100 · 5 findings · 8ac3bf1
875repo stars · whole ceedaragents/cyrus

Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit 8ac3bf1a38f4 and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 5 findings, 0 critical or high. What it does: Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “cyrus-setup-repository (ceedaragents/cyrus)”. Retrieved 27 Oct 2026. https://modelsatlas.com/skills/ceedaragents/cyrus-setup-repository

2 skills are called “cyrus-setup-repository”. You are viewing ceedaragents/cyrus.

Trust audit

Audit 0.4.1 · source read 27 Oct 2026

Trust score89/100!CAUTION B
0 critical0 high5 medium0 low0 info

CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 13,985 of 14,816 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN5
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (5)

Audit 0.4.1 · source sha 8ac3bf1a38f4 · 27 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherceedaragents GitHub organizationOwner of the repository this skill is read from
  • Source folderceedaragents/cyrus/skills/cyrus-setup-repositoryThe exact folder we audited
  • LicenceApache-2.0As the repository states it
  • Commit pinned for this verdict8ac3bf1a38f4A new audit runs when the source changes
  • Repository statusNot archivedPushed today
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.

---
name: cyrus-setup-repository
description: Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
---

**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 Repository

Adds Git repositories to Cyrus so it knows which codebases to work with.

## Step 1: Check Existing Repositories

```bash
cat ~/.cyrus/config.json 2>/dev/null | grep -o '"url"' | wc -l
```

If repositories are already configured, list them:

```bash
cat ~/.cyrus/config.json 2>/dev/null
```

Inform the user which repos are already added.

## Step 2: Add a Repository

Ask the user:

> **What is the Git URL of the repository you want Cyrus to work with?**
> (e.g., `https://github.com/yourorg/yourrepo.git`)

Run:

```bash
cyrus self-add-repo <url>
```

This clones the repo to `~/.cyrus/repos/` and registers it with the Linear workspace.

If multiple workspaces are configured, ask which workspace to use:

```bash
cyrus self-add-repo <url> "<workspace name>"
```

Verify the repo was added:

```bash
cat ~/.cyrus/config.json | grep "<repo-name>"
```

## Step 3: Add More?

Ask the user:

> **Would you like to add another repository?** (y/n)

If yes, repeat Step 2. If no, continue.

## Completion

> ✓ Repository added: `<url>`
> (repeat for each added repo)

Excerpt, first 1,482 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 8ac3bf1

Download folder ↗
git clone https://github.com/ceedaragents/cyrus
git -C cyrus checkout 8ac3bf1a38f4

The author documents no install command, so this uses the repository directly. Our verdict covers commit 8ac3bf1a38f4 only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. !CAUTION B 89 / 100

    first audit · source 8ac3bf1a38f4

Similar skills

Questions about cyrus-setup-repository

What does the cyrus-setup-repository 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-repository 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-repository 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 (8ac3bf1a38f4), read on 2026-10-27. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.