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/lbk-open/super-spec/ss-troubleshooting-workflownpx skills add lbk-open/super-spec --skill ss-troubleshooting-workflowgit clone --depth 1 https://github.com/lbk-open/super-specWrote 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/lbk-open/super-spec/ss-troubleshooting-workflow)<a href="https://agentmods.dev/skills/lbk-open/super-spec/ss-troubleshooting-workflow"><img src="https://agentmods.dev/badge/skills/lbk-open/super-spec/ss-troubleshooting-workflow.svg" alt="Measured on agentmods" 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.00079 | $0.03739 |
| Opus 5 | $0.00039 | $0.01869 |
| Sonnet 5 | $0.00016 | $0.00748 |
| Haiku 4.5 | $0.00008 | $0.00374 |
Grade A, and why
ss-troubleshooting-workflow 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 6d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting Workflow
Chains the existing ss-* skills into a single diagnose-fix-deliver flow:
ss-inspect → [Gate: root-cause confirmation] → ss-create-branch
→ ss-plan → ss-coding (built-in review) → review-acceptance loop → ss-create-pr
Core principle: thin orchestration. This skill never writes code or drafts a plan itself. It calls the other skills in order, pauses at the gates below, passes each step's output to the next, and reports progress.
Review is not run twice.
ss-codingalready enforces a post-coding review internally and returns a verdict. This workflow never invokesss-code-reviewseparately — the review-acceptance loop below is driven entirely by that verdict.
Unlike ss-feature-workflow, the root-cause report from ss-inspect replaces the proposal, and
root cause is confirmed before any branch is created — worth fixing is established before
code is touched.
When to Run
This is heavy, end-to-end orchestration: it runs a root-cause investigation, creates a branch,
spawns coding agents, runs reviews, and delivers the fix. Only run it when the user explicitly
asks for this skill or clearly wants the full diagnose-to-delivery pipeline. For a plain question
or a diagnosis-only request, do the work directly (or point to ss-inspect for diagnosis alone).
Inputs
- Problem source — an issue link, alert ID, or plain-text problem description. If missing, ask for one.
- Delivery mode —
full(default) orlite. See "Delivery Mode" below. - Investigation tier —
auto(default),L0 Local,L1 Runtime, orL2 Systemic, forwarded toss-inspect. An explicit higher tier is honored; an explicit lower tier is only a hint and must be promoted when its evidence conditions or risk boundary fail. - Skip-gates — proceed through the root-cause confirmation gate without pausing (not recommended — see Iron Rule 2).
- Decide-autonomously — resolve ambiguous choices without asking.
- Worktree preference — forwarded to
ss-create-branch.
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.
- 6d ago First seen · 227 lines · 79 tokens per session scan A e7131017f1d3
ss-troubleshooting-workflow is a skill published in the GitHub repository lbk-open/super-spec (1 stars, last pushed 15d ago), licensed Apache-2.0. It adds 79 tokens to every session and 3,739 once invoked, about $0.0004 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
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.