Agent skill · Audited from source

debug

skill · ceedaragents/cyrusApache-2.0 licenceAudited 28 Oct 2026 · source 8ac3bf1a38f4

★ 878pushed today
!CAUTIONGrade B · 89/100 · 5 findings · 8ac3bf1
878repo stars · whole ceedaragents/cyrus

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.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
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.

and 2 more with this name.

Trust audit

Audit 0.4.1 · source read 28 Oct 2026

Trust score89/100!CAUTION B
0 critical0 high5 medium0 low0 info

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

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN5
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (5)

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

Download folder ↗
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

  1. !CAUTION B 89 / 100

    first audit · source 8ac3bf1a38f4

Questions about debug

What does the debug 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 debug 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 debug access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (8ac3bf1a38f4), read on 2026-10-28. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

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.