Agent skill · Audited from source
debug
skill · ceedaragents/cyrusApache-2.0 licenceAudited 28 Oct 2026 · source 8ac3bf1a38f4
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: Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.
Cite
Cite this page
ModelsAtlas. “debug (ceedaragents/cyrus)”. Retrieved 28 Oct 2026. https://modelsatlas.com/skills/ceedaragents/debug
7 skills are called “debug”. You are viewing ceedaragents/cyrus.
- ceedaragents/cyrus★ 878!CAUTION
- Yeachan-Heo/oh-my-claudecode★ 39k✓SAFE
- gavrielc/nanoclaw★ 31k!CAUTION
- Besty0728/Unity-Skills★ 1.8k✓SAFE
- javascript-mastery-pro/skills★ 1.5k✓SAFE
and 2 more with this name.
Trust audit
Audit 0.4.1 · source read 28 Oct 2026
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
| 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 | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (5)
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 8ac3bf1a38f4 · 28 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/debugThe 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: Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.
--- name: debug description: Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix. --- # Debug Debug a reported issue using a structured reproduction-then-fix approach. ## Phase 1: Reproduction & Root Cause Analysis 1. **Investigate** — Analyze the bug report for key symptoms and error messages 2. **Trace** — Search the codebase for error occurrence patterns, trace from symptom to source 3. **Root cause** — Identify the root cause through data flow analysis and edge case checking 4. **Reproduce** — Reproduce the exact error with the smallest useful check (a command, dry run, manual flow, or automated test) 5. **Document** — Clearly document the root cause and reproduction steps ## Phase 2: Fix Implementation 1. **Plan** — Analyze the optimal fix approach based on root cause, check for similar fixes in the codebase 2. **Implement** — Make the minimal, targeted fix that addresses the root cause 3. **Verify** — Repeat the reproduction to confirm the fix and run relevant existing checks. Follow `verify-and-ship` for proportionate scope; add a regression test only when the concrete failure warrants durable coverage ## Principles - **Minimal changes** — Fix the bug, nothing more - **Targeted** — Only touch affected code paths - **Verified** — Confirm the reproduction succeeds after the fix and preserve relevant existing safeguards; a new test file is not mandatory - **No unrelated improvements** — Stay focused on the specific bug
Excerpt, first 1,526 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
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
- !CAUTION B 89 / 100
first audit · source
8ac3bf1a38f4
Similar skills
All coding & review 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
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.
ceedaragents/cyrus
Set up Cyrus end-to-end — install prerequisites, configure authentication, create integrations (Linear, GitHub, Slack), add repositories, and launch. Run this once to get Cyrus running as a background agent.
Questions about debug
What does the debug skill do?
Is debug safe to install?
What can debug access on my machine?
How current is this page?
Sources
- github.com/ceedaragents/cyrus/tree/main/skills/debug — the audited source at commit 8ac3bf1a38f4 and every finding aboveObserved · 28 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 debug skill do?
- Is debug safe to install?
- What can debug access on my machine?