ds-unstuck

ds-unstuck is a skill for Claude Code, Codex from harshii0509/designStack. It costs 47 tokens per session (1,207 once invoked), scanned A, original, MIT.

A troubleshooting process for one broken feature or page. It first gathers the symptoms, checks screenshots and browser errors when available, and explains the likely cause in plain English.

In plain words
What is it for?
Use it when a button, page, or feature stopped working or shows an error.
Why use it?
It helps identify what went wrong before changing code, and waits for approval before applying a fix.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/harshii0509/designstack/unstuck
Any agent
npx skills add harshii0509/designStack --skill unstuck
Clone the repo
git clone --depth 1 https://github.com/harshii0509/designStack

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ds-unstuck

README.md
[![agentmods](https://agentmods.dev/badge/skills/harshii0509/designstack/unstuck.svg)](https://agentmods.dev/skills/harshii0509/designstack/unstuck)
Your own site
<a href="https://agentmods.dev/skills/harshii0509/designstack/unstuck"><img src="https://agentmods.dev/badge/skills/harshii0509/designstack/unstuck.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,207 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.01207
Opus 5 $0.00023 $0.00603
Sonnet 5 $0.00009 $0.00241
Haiku 4.5 $0.00005 $0.00121

Measured 4d ago against content hash a0d65a803553, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ds-unstuck 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.

unstuck/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Preamble

"../lib/env.sh" "unstuck"

What this skill does

Something stopped working. You're going to diagnose it visually, explain it in plain English, then propose exactly one fix — and wait for approval before any code is touched.

This skill never writes code until the user says yes.

Step 1 — Understand the problem

Ask the user (if it's not already clear from context):

"What happened? Describe it like you'd tell a friend — 'the button doesn't do anything when I click it', 'the page looks broken', 'I get a red error message', etc."

Also check the conversation history for any error messages, stack traces, or descriptions already provided.

Step 2 — Take a screenshot (if browse available)

If BROWSE is not NOT_FOUND and the project has a running URL:

Ask: "Is your project running right now? What's the URL?"

If yes:

$B goto <URL>
$B screenshot /tmp/dstack-unstuck.png
$B console --errors

If the URL is not reachable:

"It looks like your project isn't running right now. To start it, open your terminal and type npm run dev (or npm start) — then tell me the URL, usually http://localhost:3000. I'll wait."

Do not continue until the user confirms the project is running.

Show the screenshot to the user via the Read tool so they can see it.

Also check the browser console for errors:

$B console

Note any red errors in the console output.

If BROWSE is NOT_FOUND: skip screenshots. Work from the error message and code context only.

Step 3 — Diagnose in plain English

Follow the jargon rules in lib/plain-language.md when diagnosing — no technical terms.

Write ONE sentence that describes exactly what's wrong. No technical jargon. Examples:

  • "The submit button isn't working because it's pointing to a page that doesn't exist yet."
  • "The page looks blank because there's an error in the data it's trying to load."
  • "The layout is broken because a piece of the page is missing a required setting."
  • "The image isn't showing up because the file path has a typo."
  • "The login isn't working because the connection to your database timed out."

Read the full file on GitHub · 146 lines

Changes

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.

  1. 4d ago First seen · 146 lines · 47 tokens per session scan A a0d65a803553

Subscribe to this mod's changes

ds-unstuck is a skill published in the GitHub repository harshii0509/designStack (13 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,207 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens