Cyrus Setup PrerequisitesCAUTION
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-13Install
Commands as the repository documents them. They are shown, not run.
npm install -g cyrus-ai
Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What 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-prerequisites description: Check and install prerequisites for Cyrus — Node.js, jq, gh CLI, and the cyrus-ai npm package. --- **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 Prerequisites Checks system prerequisites and installs `cyrus-ai`. ## Step 1: Detect Package Manager If the user hasn't already specified their preferred package manager, ask: > **Which package manager do you prefer?** npm, pnpm, bun, or yarn? Store the answer for use in this and subsequent skills. ## Step 2: Check System Dependencies Run the following checks and report results: ```bash # Node.js >= 18 node --version # jq (required for Claude Code parsing) jq --version # GitHub CLI (required for GitHub integration) gh --version ``` For each missing dependency, provide the install command: | Dependency | macOS | Linux/Ubuntu | |-----------|-------|--------------| | Node.js | `brew install node` | `curl -fsSL https://deb.nodesource.com/setup_22.x \| sudo -E bash - && sudo apt install -y nodejs` | | jq | `brew install jq` | `sudo apt install -y jq` | | gh | `brew install gh` | See https://github.com/cli/cli/blob/trunk/docs/install_linux.md | If all dependencies are present, print a checkmark for each and continue. If any are missing, offer to install them (detect OS via `uname`). Wait for user confirmation before installing. ## Step 3: Check for agent-browser (Optional) If the user selected any integration surface (Linear, GitHub, Slack), check for `agent-browser`: ```bash which agent-browser ``` **If installed**, ensure it's up to date: ```bash npm update -g agent-browser ``` **If not found**, inform the user: > `agent-browser` is optional but enables automated app creation for Linear/GitHub/Slack. Without it, you'll be guided through manual setup steps instead. > > Install with: `npm install -g agent-browser` Do NOT block on this — it's optional. Note whether it's available for downstream skills. ## Step 4: Install cyrus-ai Check if already installed: ```bash which cyrus ``` If not found, install using the user's preferred package manager: ```bash # npm npm install -g cyrus-ai # pnpm pnpm install -g cyrus-ai # bun bun install -g cyrus-ai # yarn yarn global add cyrus-ai ``` Verify installation: ```bash cyrus --version ``` ## Step 5: Ensure ~/.cyrus directory exists ```bash mkdir -p ~/.cyrus ``` If `~/.cyrus/.env` already exists, note it and inform the user that existing values will be preserved. ## Completion Print a summary: ``` Prerequisites: ✓ Node.js v22.x ✓ jq 1.7 ✓ gh 2.x ✓ cyrus-ai installed ✓ agent-browser available (or: ⚠ not installed — manual setup mode) ```
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-prerequisites.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 Prerequisites 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 Prerequisites 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 Prerequisites access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
What do I need installed to use Cyrus Setup Prerequisites?
Its own instructions reference uname. Dependencies are pinned to exact versions.
Which assistants does Cyrus Setup Prerequisites work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
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.