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 Notysoty/openagentskills --skill troubleshooting-guide-buildergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/troubleshooting-guide-builder)<a href="https://agentmods.dev/skills/notysoty/openagentskills/troubleshooting-guide-builder"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/troubleshooting-guide-builder/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/notysoty/openagentskills/troubleshooting-guide-builder"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/troubleshooting-guide-builder.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.00025 | $0.01658 |
| Opus 5 | $0.00013 | $0.00829 |
| Sonnet 5 | $0.00005 | $0.00332 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
Troubleshooting Guide Builder 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 9d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting Guide Builder
What this skill does
This skill builds a structured troubleshooting guide that maps symptoms to causes to fixes for any software tool, API, or system. Each entry follows a consistent format: what the user experiences, why it happens, and exactly how to fix it — including specific commands, configuration changes, or code snippets. The result is a guide that developers or support staff can scan quickly to resolve issues without digging through source code or guessing.
Use this when writing documentation for a new tool, after an incident reveals a common failure mode, when your support team keeps answering the same questions, or when preparing runbooks for operational issues.
How to use
Claude Code / Cline
Copy this file to .agents/skills/troubleshooting-guide-builder/SKILL.md in your project root.
Then ask:
- "Use the Troubleshooting Guide Builder skill to write a troubleshooting guide for our CLI tool."
- "Build a troubleshooting guide for the most common deployment errors using the Troubleshooting Guide Builder skill."
Provide:
- A description of the tool, API, or system
- A list of known issues, error messages, or symptoms (ideally from real support cases)
- Any relevant error codes, configuration options, or environment details
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Provide the tool description and known issues.
Codex
Paste the tool description, error messages, and any existing support notes. Ask Codex to follow the instructions below.
The Prompt / Instructions for the Agent
When asked to build a troubleshooting guide, follow these steps:
Step 1 — Gather known issues
If given a list of symptoms or errors, use them as the basis. If not, generate a comprehensive list of likely issues by thinking through:
- Installation and setup failures
- Authentication and permissions errors
- Configuration mistakes
- Rate limits and quota errors
- Network and connectivity issues
- Common misunderstandings about how the tool works
- Environment-specific issues (OS, version, dependencies)
- Data format or validation errors
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.
- 9d ago First seen · 205 lines · 25 tokens per session scan A cea288e0840e
Troubleshooting Guide Builder is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 26d ago), licensed MIT. It adds 25 tokens to every session and 1,658 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-31.
Other skills, from other repositories
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-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.
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.
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.
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…
lsp
Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.