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.
npx agentmods add skills/cyrusagents/cyrus/debugnpx skills add cyrusagents/cyrus --skill debuggit clone --depth 1 https://github.com/cyrusagents/cyrusWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00025 | $0.00294 |
| Opus 5 | $0.00013 | $0.00147 |
| Sonnet 5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
debug scanned grade A with 0 findings 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Debug
Debug a reported issue using a structured reproduction-then-fix approach.
Phase 1: Reproduction & Root Cause Analysis
- Investigate — Analyze the bug report for key symptoms and error messages
- Trace — Search the codebase for error occurrence patterns, trace from symptom to source
- Root cause — Identify the root cause through data flow analysis and edge case checking
- Reproduce — Create a minimal failing test case that reproduces the exact error
- Document — Clearly document the root cause and reproduction steps
Phase 2: Fix Implementation
- Plan — Analyze the optimal fix approach based on root cause, check for similar fixes in the codebase
- Implement — Make the minimal, targeted fix that addresses the root cause
- Verify — Run the failing test to confirm it passes, then run the full test suite to check for regressions
Principles
- Minimal changes — Fix the bug, nothing more
- Targeted — Only touch affected code paths
- Tested — The fix must make the failing test pass and not break existing tests
- No unrelated improvements — Stay focused on the specific bug
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.
- 2d ago First seen · 30 lines · 25 tokens per session scan A a5262d32421f
debug is a skill published in the GitHub repository cyrusagents/cyrus (792 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 294 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
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…
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…
gsap-core
Official GSAP skill for the core API — gsap.to(), from(), fromTo(), easing, duration, stagger, defaults, gsap.matchMedia() (responsive, prefers-reduced-motion). Use when the user asks for a JavaScript animation library, animation in React/Vue/vanilla, GSAP tweens, easing, basic animation, responsive or reduced-motion…
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.