cyrus-setup-claude-auth
Skill888 starsChanged 53 days agoApache-2.0View on GitHub
Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cyrusagents/cyrusword for word, first seen Sep 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cyrusagents/cyrus★ 902100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- googleSkill
- release-core-testSkill
- cyrus-setup-endpointSkill
- cyrus-setup-githubSkill
- cyrus-setup-gitlabSkill
- cyrus-setup-launchSkill
- cyrus-setup-linearSkill
- cyrus-setup-prerequisitesSkill
- cyrus-setup-repositorySkill
- cyrus-setupSkill
- cyrus-setup-slackSkill
- debugSkill
- f1-test-driveSkill
- implementationSkill
- investigateSkill
- releaseSkill
- summarizeSkill
- verify-and-shipSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Check if credentials are already configured:
- Distinctive: line 20
If the count is >= 1, inform the user:
- Very specific: line 40
CRITICAL: Secrets must NEVER appear in the conversation: Do not explore ~/.claude/ looking for credential files.
- Very specific: line 50
Check if claude is authenticated on this machine:
- Very specific: line 56
If authenticated, instruct the user to run claude setup-token which will output a token.
- Distinctive: line 151
After the user runs the command, verify the key was written:
- Distinctive: line 157
If the count is 0, the credential was not saved.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 Claude Auth
Configures Claude Code credentials so Cyrus can run AI sessions.
Step 1: Check Existing Auth
Check if credentials are already configured:
grep -c -E '^(ANTHROPIC_API_KEY|CLAUDE_CODE_OAUTH_TOKEN)=' ~/.cyrus/.env 2>/dev/null || echo "0"If the count is >= 1, inform the user:
Claude Code authentication is already configured. Skipping this step. To reconfigure, remove the existing key from
~/.cyrus/.envand re-run this skill.
Skip to completion.
Step 2: Choose Auth Method
Ask the user:
How would you like to authenticate Claude Code?
- Current account (easiest) — use the credentials from your active
claudeCLI session- API Key — from console.anthropic.com
- Separate OAuth token — run
claude setup-tokento generate a token for a specific account- Third-Party Provider — Vertex AI, AWS Bedrock, Azure, etc.
Step 3: Configure Credentials
CRITICAL: Secrets must NEVER appear in the conversation. Do not explore ~/.claude/ looking for credential files. Use only the methods below.
Detect the OS for the right clipboard command:
uname -sOption 1: Current Account
Check if claude is authenticated on this machine:
claude auth statusIf authenticated, instruct the user to run claude setup-token which will output a token.
To capture it safely, append a placeholder line to the env file, then open it in a GUI window so the user can paste the token:
grep -q '^CLAUDE_CODE_OAUTH_TOKEN=' ~/.cyrus/.env || echo 'CLAUDE_CODE_OAUTH_TOKEN=' >> ~/.cyrus/.envThen open the file in a separate window — use whatever GUI editor is available:
# macOS: VS Code if available, otherwise TextEdit
code --new-window ~/.cyrus/.env 2>/dev/null || open -a TextEdit ~/.cyrus/.env
# Linux
code ~/.cyrus/.env 2>/dev/null || xdg-open ~/.cyrus/.envTell the user:
- Run
claude setup-tokenin a separate terminal- Copy the token it outputs
- I've opened
~/.cyrus/.env— find theCLAUDE_CODE_OAUTH_TOKEN=line- Paste the token right after the
=(no spaces, no newline)- Save and close the file
Option 2: API Key
Instruct the user to copy their API key from the Anthropic Console, then provide the appropriate command:
macOS:
printf 'ANTHROPIC_API_KEY=%s\n' "$(pbpaste)" >> ~/.cyrus/.envLinux:
printf 'ANTHROPIC_API_KEY=%s\n' "$(xclip -selection clipboard -o)" >> ~/.cyrus/.envUniversal fallback:
read -s -p "Paste your Anthropic API key: " val && printf 'ANTHROPIC_API_KEY=%s\n' "$val" >> ~/.cyrus/.env && echo " ✓ Saved"Option 3: Separate OAuth Token
This is for when the user wants to generate a token for a different account than the one currently logged in (e.g., running claude setup-token on another machine).
Append the placeholder, then open the file for the user to paste:
grep -q '^CLAUDE_CODE_OAUTH_TOKEN=' ~/.cyrus/.env || echo 'CLAUDE_CODE_OAUTH_TOKEN=' >> ~/.cyrus/.env# macOS
code --new-window ~/.cyrus/.env 2>/dev/null || open -a TextEdit ~/.cyrus/.env
# Linux
code ~/.cyrus/.env 2>/dev/null || xdg-open ~/.cyrus/.envTell the user:
- On the other machine, run
claude setup-token- Copy the token it outputs
- I've opened
~/.cyrus/.env— findCLAUDE_CODE_OAUTH_TOKEN=and paste the token after the=- Save and close
Option 4: Third-Party Provider
Inform the user:
For third-party providers, you'll need to set provider-specific environment variables. See Third-Party Integrations for details.
Common configurations:
AWS Bedrock:
CLAUDE_CODE_USE_BEDROCK=1 AWS_REGION=us-east-1Google Vertex AI:
CLAUDE_CODE_USE_VERTEX=1 CLOUD_ML_REGION=us-east5 ANTHROPIC_VERTEX_PROJECT_ID=your-project-id
Guide the user to add the appropriate variables to ~/.cyrus/.env using the clipboard-to-env pattern.
Step 4: Verify
After the user runs the command, verify the key was written:
grep -c -E '^(ANTHROPIC_API_KEY|CLAUDE_CODE_OAUTH_TOKEN|CLAUDE_CODE_USE_BEDROCK|CLAUDE_CODE_USE_VERTEX)=' ~/.cyrus/.envIf the count is 0, the credential was not saved. Ask the user to try again.
Completion
✓ Claude Code authentication configured.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

