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 Timmy6942025/opencode-builder-skill --skill opencode-troubleshootinggit clone --depth 1 https://github.com/Timmy6942025/opencode-builder-skillWrote 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/timmy6942025/opencode-builder-skill/opencode-troubleshooting)<a href="https://agentmods.dev/skills/timmy6942025/opencode-builder-skill/opencode-troubleshooting"><img src="https://agentmods.dev/badge/skills/timmy6942025/opencode-builder-skill/opencode-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/timmy6942025/opencode-builder-skill/opencode-troubleshooting"><img src="https://agentmods.dev/badge/skills/timmy6942025/opencode-builder-skill/opencode-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.00118 | $0.04620 |
| Opus 5.5 | $0.00047 | $0.01848 |
| Sonnet 5.5 | $0.00024 | $0.00924 |
| Haiku 4.5 | $0.00012 | $0.00462 |
Grade C, and why
opencode-troubleshooting scanned grade C with 2 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.local/share/opencode Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Try `curl https://api.openai.com/v1/models` (or equivalent for your provider) How it starts
The opening of the file, as written. The whole thing — 604 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode Troubleshooting
📚 Official Docs: For the latest information, always refer to the official documentation: https://opencode.ai/docs/troubleshooting/
OpenCode is an AI-powered coding assistant available as a CLI, TUI, web interface, and desktop app. When something goes wrong — the app won't start, models fail to load, authentication breaks, or the UI is unresponsive — this skill provides comprehensive diagnostic and resolution procedures. Start by checking logs and storage, then work through the specific issue category.
Table of Contents
Logs
Log files are the first place to look when diagnosing any issue with OpenCode. They contain detailed information about startup, provider connections, API calls, errors, and internal state transitions.
Log File Locations
| Platform | Path |
|---|---|
| macOS | ~/.local/share/opencode/log/ |
| Linux | ~/.local/share/opencode/log/ |
| Windows | Press WIN+R and paste %USERPROFILE%\.local\share\opencode\log |
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.
- 1mo ago First seen · 604 lines · 118 tokens per session scan C cc8e567f0778
opencode-troubleshooting is a skill published in the GitHub repository Timmy6942025/opencode-builder-skill (2 stars, last pushed 4mo ago), licensed MIT. It adds 118 tokens to every session and 4,620 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ast-grep
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.
debugging
Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.
lcx-doctor
Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install…
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
lsp
Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.