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 badsectorlabs/ludus-skills --skill troubleshootinggit clone --depth 1 https://github.com/badsectorlabs/ludus-skillsWrote 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/badsectorlabs/ludus-skills/troubleshooting)<a href="https://agentmods.dev/skills/badsectorlabs/ludus-skills/troubleshooting"><img src="https://agentmods.dev/badge/skills/badsectorlabs/ludus-skills/troubleshooting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/badsectorlabs/ludus-skills/troubleshooting"><img src="https://agentmods.dev/badge/skills/badsectorlabs/ludus-skills/troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00050 | $0.00445 |
| Opus 5 | $0.00025 | $0.00222 |
| Sonnet 5 | $0.00010 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
troubleshooting 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 10d 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
Ludus Troubleshooting
Use this skill to triage user-reported failures quickly, categorize errors, and provide targeted remediation steps.
Diagnostic Workflow
- Gather context and exact error output.
- Check range deployment status and recent errors.
- Review deployment logs for failure details.
- Identify the failure category using the known error catalog.
- Inspect the current range config for misconfigurations.
- Provide targeted fixes with concrete steps.
- Define clear verification steps to confirm recovery.
Key Diagnostic Information
When triaging, gather these in order of usefulness:
- Range status — is the deployment running, failed, or complete?
- Deployment errors — the most recent error output from a deploy.
- Deployment logs — full log stream for tracing failure context.
- Template status — are required templates built and available?
- Range config — does the YAML match what the user intended?
- Testing mode status — is testing mode active, and are network rules in effect?
Common Patterns
- Network issues often trace back to dnsmasq or NAT bridge state.
- Ansible failures often involve WinRM (Windows) or SSH reachability (Linux).
- Domain join failures usually involve DNS ordering or timing.
- Template failures are commonly ISO download or disk-space related.
References
- Use
references/common-errors.mdfor known errors, root causes, and fix procedures. - Use
https://docs.ludus.cloud/docs/troubleshooting/clientfor client and CLI troubleshooting details. - Use
https://docs.ludus.cloud/docs/troubleshooting/network/andhttps://docs.ludus.cloud/docs/troubleshooting/wireguard/for network and connectivity issues. - For uninstalling Ludus, direct users to the official guide at
https://docs.ludus.cloud/docs/troubleshooting/uninstallrather than performing the steps yourself.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 44 lines · 50 tokens per session scan A 737765dd23a0
troubleshooting is a skill published in the GitHub repository badsectorlabs/ludus-skills (9 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 445 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-08-31.
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.