Agent skill · Audited from source
cyrus-setup-endpoint
skill · ceedaragents/cyrusApache-2.0 licenceAudited 22 Oct 2026 · source ad5d72f18452
Is it safe? No — BLOCK, grade D (69/100). We read this skill's source at commit ad5d72f18452 and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 6 findings, 1 critical or high. What it does: Configure the public webhook endpoint for Cyrus — ngrok, Cloudflare Tunnel, or custom URL.
Cite
Cite this page
ModelsAtlas. “cyrus-setup-endpoint (ceedaragents/cyrus)”. Retrieved 22 Oct 2026. https://modelsatlas.com/skills/ceedaragents/cyrus-setup-endpoint
Blocked. The page stays public so you can check this skill if someone recommended it to you. The audit found 1 critical or high finding, starting with “Prompt injection” in SKILL.md:35. Do not install it without reading them.
2 skills are called “cyrus-setup-endpoint”. You are viewing ceedaragents/cyrus. 2 of them are BLOCK.
- ceedaragents/cyrus★ 861✕BLOCK
- cyrusagents/cyrus★ 856✕BLOCK
Trust audit
Audit 0.4.1 · source read 22 Oct 2026
BLOCK means the audit found something that could harm you or your machine. Grade D is shared by 642 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
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | WARN | 5 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | FAIL | 1 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: instruction override, no behavioural pass.
Findings (6)
HIGHPrompt injectionprompt.hide_from_user · SKILL.md:35
**Important:** ngrok's free tier includes a permanent static domain — do NOT tell the user this is a paid feature or that URLs change on restart. Every free ngrok account gets one static domain at htt
- Why
- asks the agent to act without the user's knowledge
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/cyrus-setup
.claude/skills/cyrus-setup
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/cyrus-setup-claude-auth
.claude/skills/cyrus-setup-claude-auth
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/cyrus-setup-endpoint
.claude/skills/cyrus-setup-endpoint
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/cyrus-setup-github
.claude/skills/cyrus-setup-github
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/cyrus-setup-gitlab
.claude/skills/cyrus-setup-gitlab
- Why
- link not followed
- Fix
- —
Audit 0.4.1 · source sha ad5d72f18452 · 22 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-endpointThe exact folder we audited
- LicenceApache-2.0As the repository states it
- Commit pinned for this verdictad5d72f18452A 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: Configure the public webhook endpoint for Cyrus — ngrok, Cloudflare Tunnel, or custom URL.
---
name: cyrus-setup-endpoint
description: Configure the public webhook endpoint for Cyrus — ngrok, Cloudflare Tunnel, or custom URL.
---
**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 Endpoint
Configures a public URL so Linear (and other integrations) can send webhooks to your Cyrus instance.
## Step 1: Check Existing Configuration
```bash
grep -E '^CYRUS_BASE_URL=' ~/.cyrus/.env 2>/dev/null
```
If `CYRUS_BASE_URL` is already set, inform the user:
> Webhook endpoint already configured: `<value>`
> To reconfigure, remove `CYRUS_BASE_URL` from `~/.cyrus/.env` and re-run this skill.
Skip to Step 4 (write port/webhooks if missing).
## Step 2: Choose Endpoint Method
Ask the user:
> **How will you expose Cyrus to the internet for webhooks?**
>
> 1. **ngrok** (recommended — every free account includes one static domain that persists across restarts)
> 2. **Cloudflare Tunnel** (permanent, requires Cloudflare account)
> 3. **Own URL** (you already have a public URL/domain)
**Important:** ngrok's free tier includes a permanent static domain — do NOT tell the user this is a paid feature or that URLs change on restart. Every free ngrok account gets one static domain at https://dashboard.ngrok.com/domains.
## Step 3: Configure Endpoint
### Option 1: ngrok
#### 3a. Check if ngrok is installed
```bash
which ngrok
```
If not installed, provide install instructions:
**macOS:**
```bash
brew install ngrok
```
**Linux:**
```bash
curl -sSL https://ngrok-agent.s3.amazonaws.com/ngrok-v3-stable-linux-amd64.tgz | sudo tar xvz -C /usr/local/bin
```
#### 3b. Guide ngrok domain setup
Instruct the user:
> ngrok provides a free static domain so your URL doesn't change between restarts.
>
> 1. Sign up or log in at https://dashboard.ngrok.com
> 2. Go to https://dashboard.ngrok.com/domains
> 3. Copy your free static domain (e.g., `your-name-here.ngrok-free.app`)
> 4. Go to https://dashboard.ngrok.com/get-started/your-authtoken and copy your authtoken
Ask the user to provide:
- Their ngrok domain
- Their ngrok authtoken
**CRITICAL: The authtoken is a secret. Use clipboard-to-file commands.**
#### 3c. Write ngrok configuration
Write the ngrok config so it can be started with `ngrok start cyrus`:
```bash
mkdir -p ~/.config/ngrok
```
Then write `~/.config/ngrok/ngrok.yml` (merge with existing if present):
```yaml
version: 3
agent:
authtoken: <token>
endpoints:
- name: cyrus
url: <domain>
upstream:
url: 3456
```
For the authtoken, use a clipboard-to-file approach:
**macOS:**
```bash
# User copies authtoken, then runs:
NGROK_TOKEN=$(pbpaste) && cat > ~/.config/ngrok/ngrok.yml << EOF
version: 3
agent:
authtoken: $NGROK_TOKEN
endpoints:
- name: cyrus
url: <domain>
upstream:
url: 3456
EOF
```
**Universal fallback:**
```bash
read -s -p "Paste your ngrok authtoken: " NGROK_TOKEN && cat > ~/.config/ngrok/ngrok.yml << EOF
version: 3
agent:
authtoken: $NGROK_TOKEN
endpoints:
- name: cyrus
url: <domain>
upstream:
url: 3456
EOF
echo " ✓ Saved"
```
#### 3d. Write CYRUS_BASE_URL
```bash
printf 'CYRUS_BASE_URL=https://%s\n' "<domain>" >> ~/.cyrus/.env
```
Where `<domain>` is the ngrok domain the user provided (e.g., `your-name-here.ngrok-free.app`).
Inform the user:
> To start ngrok, run: `ngrok start cyrus`
> Run this in a separate terminal before starting Cyrus.
### Option 2: Cloudflare Tunnel
Ask the user for:
- Their Cloudflare Tunnel token
- Their tunnel hostname (e.g., `cyrus.yourdomain.com`)
**Token is a secret — use clipboard-to-env:**
**macOS:**
```bash
printf 'CLOUDFLARE_TOKEN=%s\n' "$(pbpaste)" >> ~/.cyrus/.env
```
**Universal fallback:**
```bash
read -s -p "Paste your Cloudflare token: " val && printf 'CLOUDFLARE_TOKEN=%s\n' "$val" >> ~/.cyrus/.env && echo " ✓ Saved"
```
Then write the base URL (not a secret — agent can write directly):
```bash
printf 'CYRUS_BASE_URL=https://<hostname>\n' >> ~/.cyrus/.env
```
### Option 3: Own URL
Ask the user for their URL. Validate it starts with `https://`.
```bash
printf 'CYRUS_BASE_URL=%s\n' "<url>" >> ~/.cyrus/.env
```
## Step 4: Write Common Config
Ensure these are present in `~/.cyrus/.env` (add only if missing):
```bash
grep -q '^CYRUS_SERVER_PORT=' ~/.cyrus/.env 2>/dev/null || printf 'CYRUS_SERVER_PORT=3456\n' >> ~/.cyrus/.env
grep -q '^LINEAR_DIRECT_WEBHOOKS=' ~/.cyrus/.env 2>/dev/null || printf 'LINEAR_DIRECT_WEBHOOKS=true\n' >> ~/.cyrus/.env
grep -q '^CYRUS_HOST_EXTERNAL=' ~/.cyrus/.env 2>/dev/null || printf 'CYRUS_HOST_EXTERNAL=true\n' >> ~/.cyrus/.env
```
`LINEAR_DIRECT_WEBHOOKS=true` enables direct Linear webhook signature verification. `CYRUS_HOST_EXTERNAL=true` enables direct Slack and GitHub webhook signature verification. Both are required for self-hosted setups where webhooks come directly from the services (not forwarded through CYHOST).
## Completion
> ✓ Webhook endpoint configured: `<CYRUS_BASE_URL>`
> ✓ Server port: 3456
> ✓ Direct webhooks: enabledExcerpt, first 5,176 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 ad5d72f
git clone https://github.com/ceedaragents/cyrus git -C cyrus checkout ad5d72f18452
The author documents no install command, so this uses the repository directly. Our verdict covers commit ad5d72f18452 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
- ✕BLOCK D 69 / 100
first audit · source
ad5d72f18452
Similar skills
ceedaragents/cyrus
Assess F1 applicability, then validate changed product workflows or the F1 harness end-to-end. Skip drives and reports when no relevant workflow behavior changes.
ceedaragents/cyrus
Search the web for information. Use when you need to look something up, find current information, or research a topic.
ceedaragents/cyrus
Implement the requested changes. Write production-ready code, follow existing patterns, and use proportionate verification.
ceedaragents/cyrus
Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.
ceedaragents/cyrus
Check and install prerequisites for Cyrus — Node.js, jq, gh CLI, and the cyrus-ai npm package.
ceedaragents/cyrus
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
Questions about cyrus-setup-endpoint
What does the cyrus-setup-endpoint skill do?
Is cyrus-setup-endpoint safe to install?
What can cyrus-setup-endpoint access on my machine?
How current is this page?
Sources
- github.com/ceedaragents/cyrus/tree/main/skills/cyrus-setup-endpo — the audited source at commit ad5d72f18452 and every finding aboveObserved · 22 Oct 2026
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.
- What does the cyrus-setup-endpoint skill do?
- Is cyrus-setup-endpoint safe to install?
- What can cyrus-setup-endpoint access on my machine?