cyrus-setup

cyrus-setup is a skill for Claude Code, Codex from cyrusagents/cyrus. It costs 46 tokens per session (2,164 once invoked), scanned B, original, Apache-2.0.

A setup guide for running Cyrus, a background coding agent that can respond to work from Linear, Slack, and GitHub. It covers prerequisites, sign-in settings, integrations, repositories, and launch.

In plain words
What is it for?
Use it to install and configure Cyrus, connect Linear, GitHub, and Slack, add repositories, and start the agent.
Why use it?
It brings the setup steps into one guided process instead of requiring you to configure each part separately. It also keeps sensitive configuration files from being directly read or edited.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Install

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.

agentmods
npx agentmods add skills/cyrusagents/cyrus/cyrus-setup
Any agent
npx skills add cyrusagents/cyrus --skill cyrus-setup
Clone the repo
git clone --depth 1 https://github.com/cyrusagents/cyrus

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cyrus-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/cyrusagents/cyrus/cyrus-setup.svg)](https://agentmods.dev/skills/cyrusagents/cyrus/cyrus-setup)
Your own site
<a href="https://agentmods.dev/skills/cyrusagents/cyrus/cyrus-setup"><img src="https://agentmods.dev/badge/skills/cyrusagents/cyrus/cyrus-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,164 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.02164
Opus 5 $0.00023 $0.01082
Sonnet 5 $0.00009 $0.00433
Haiku 4.5 $0.00005 $0.00216

Measured 6d ago against content hash f48df8e9ebb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

cyrus-setup scanned grade B with 1 finding 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 6d 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

To find the files, look for them relative to this file's directory (go up one level, then into the sub-skill directory). For example, if this file is at `~/.claude/skills/cyrus-setup/SKILL.md`, the sub-skills are at `~/.
skills/cyrus-setup/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cyrus Setup

One-command setup for self-hosted Cyrus. This orchestrator walks you through everything needed to run Claude Code as a background agent from Linear, Slack, and GitHub.

CRITICAL Rules

Never Read or Write ~/.cyrus/.env Directly

FORBIDDEN: Do NOT use Read, Edit, or Write tools on ~/.cyrus/.env or any file inside ~/.cyrus/. This file contains secrets (API keys, tokens, signing secrets). All interaction with this file MUST go through Bash commands (grep, printf >> ..., etc.) which the user can see and approve. Never read its contents into the conversation context.

Browser Automation

The goal of browser automation in this skill is to reduce sign-in and setup fatigue — the agent navigates web UIs, fills forms, and scrapes credentials so the user doesn't have to do it all manually.

Three modes, in order of preference:

  1. claude-in-chrome (preferred when available) — if the user is running Claude Code and has the claude-in-chrome MCP extension connected, use it. This has the huge advantage of using the user's existing Chrome with all their signed-in sessions (Linear, Slack, GitHub). Check availability by seeing if mcp__claude-in-chrome__* tools exist.
  2. agent-browser CLI — a standalone Playwright-based binary invoked via Bash. Requires launching a fresh Chrome profile with remote debugging enabled (the user will need to sign in to services in that profile). Check with which agent-browser.
  3. Manual guided flow — the user follows the agent's step-by-step instructions and does the clicks themselves. Always available as Path B in each sub-skill.

Determining which mode to use:

  1. First, check if claude-in-chrome MCP tools are available in the current session. If yes, use those — no setup needed.
  2. If not, check which agent-browser. If installed, launch a fresh Chrome profile (see below).
  3. If neither is available, ask the user: install agent-browser, or follow manual instructions?

Read the full file on GitHub · 215 lines

Changes

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.

  1. 6d ago First seen · 215 lines · 46 tokens per session scan B f48df8e9ebb8

Subscribe to this mod's changes

cyrus-setup is a skill published in the GitHub repository cyrusagents/cyrus (797 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 2,164 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

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.

langchain-ai/open-swe · 51 tokens

bootstrap-repo-analysis

First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the…

langchain-ai/open-swe · 73 tokens

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

langchain-ai/open-swe · 30 tokens

write-oep

Draft an Open SWE Enhancement Proposal using the repository's OEP process and template. Use when the user asks to create, write, or propose an OEP or invokes /write-oep.

langchain-ai/open-swe · 42 tokens

continual-learning

Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…

langchain-ai/open-swe · 89 tokens

linearis

Manage Linear.app work from the command line with the linearis CLI (bins linearis / linear), which outputs JSON: issues/tickets, projects, cycles (sprints), milestones, initiatives (roadmap), documents, labels, teams, users, and issue discussions/comments. Use when the user mentions Linear, a ticket identifier like…

linearis-oss/linearis · 111 tokens