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 skills add RudyCity/superagent --skill non-linear-debugginggit clone --depth 1 https://github.com/RudyCity/superagentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rudycity/superagent/non-linear-debugging)<a href="https://agentmods.dev/skills/rudycity/superagent/non-linear-debugging"><img src="https://agentmods.dev/badge/skills/rudycity/superagent/non-linear-debugging.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00060 | $0.01517 |
| Opus 5 | $0.00030 | $0.00758 |
| Sonnet 5 | $0.00012 | $0.00303 |
| Haiku 4.5 | $0.00006 | $0.00152 |
Grade A, and why
non-linear-debugging 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Non-Linear Debugging & Bug Discovery Engine
Enables the AI agent to systematically diagnose, analyze, and resolve complex software errors, obscure bugs, race conditions, memory/state leaks, and system anomalies using non-linear, graph-based cognitive methodologies instead of sequential, line-by-line debugging.
When to Use This Skill
- Trigger keywords: "non-linear debug", "debug error", "analyze error", "find bug", "cari bug", "investigasi error", "non linear bug finding", "root cause triangulation", "complex failure analysis".
- When a bug involves asynchronous event loops, multi-service communication (e.g. t-line ↔ SuperAgent bridge), race conditions, state synchronization mismatches, or multi-component failure cascades.
- When traditional step-by-step linear tracing fails or is too slow due to missing or noisy error logs.
- When facing ambiguous symptoms where multiple independent factors might be interacting.
Core Non-Linear Debugging Paradigms
┌───────────────────────────────────────┐
│ Forward Tracing (Source ──►) │
└───────────────────┬───────────────────┘
│
▼
┌──────────────────┐ ┌─────────────────────┐ ┌──────────────────┐
│ Hypothesis H₁ │───►│ COLLISION NODE │◄───│ Hypothesis H₃ │
│ (State / Timing) │ │ (Root Cause Δ) │ │ (Config / IPC) │
└──────────────────┘ └─────────────────────┘ └──────────────────┘
▲
│
┌───────────────────┴───────────────────┐
│ Backward Tracing (◄── Sink/Crash) │
└───────────────────────────────────────┘
1. Bidirectional Cause-Effect Triangulation (Backward-Forward Tracing)
- Backward Tracing ($\leftarrow \text{Crash Sink}$): Trace upstream from where the exception is thrown, state is mutated, or process crashes.
- Forward Tracing ($\text{Input Source} \rightarrow$): Trace downstream from initial request, user trigger, or state payload entry.
- Collision Node Identification ($\otimes$): Identify the exact intersection node where valid forward state violates backward invariants.
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.
- 4d ago First seen · 109 lines · 60 tokens per session scan A 32a800fae94d
non-linear-debugging is a skill published in the GitHub repository RudyCity/superagent (21 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 1,517 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.