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 sso-ss/vibe-ship-it --skill unstuckgit clone --depth 1 https://github.com/sso-ss/vibe-ship-itWrote 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/sso-ss/vibe-ship-it/unstuck)<a href="https://agentmods.dev/skills/sso-ss/vibe-ship-it/unstuck"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/unstuck/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/sso-ss/vibe-ship-it/unstuck"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/unstuck.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.00088 | $0.01017 |
| Opus 5 | $0.00044 | $0.00508 |
| Sonnet 5 | $0.00018 | $0.00203 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
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 12d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unstuck
The momentum-preservation skill. When a designer hits a wall, get them back to a working state as fast as possible. Explain after.
Detection Signals
Activate when you see:
- Short frustrated messages: "ugh", "help", "stuck", "wtf"
- Error descriptions: "this doesn't work", "it broke", "nothing happens"
- Repeated attempts at the same thing
- Same error appearing multiple times
- Designer pasting error messages
- Questions like "why doesn't this work?"
Response Protocol
Step 1: Acknowledge (1 sentence)
"Got it, let me take a look."
Do NOT say: "What seems to be the problem?" or "Can you describe the error?" or "What were you trying to do?"
They already told you. Or the context tells you. Diagnose from what you can see.
Step 2: Diagnose Silently
Check in this order:
- Terminal output — any errors visible?
- Browser console — any errors in the page?
- Recent file changes — what did they (or you) change last?
- Dev server — is it running? Did it crash?
- Dependencies — any missing packages?
- Environment — any missing env vars?
Step 3: Fix
Fix the problem. Don't describe what you're about to do. Just do it.
Step 4: Show Working Result
"That's working now. Check your browser."
Step 5: Brief Explanation (1-2 sentences, only if helpful)
"The issue was [X]. This happens when [Y]. No worries."
Do NOT:
- Launch into a teaching moment
- Explain the underlying architecture
- Suggest they should have done it differently
- Recommend preventive measures
Step 6: Momentum Restore
"Want to keep going?"
Common Problems & Fast Fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Blank page | Server component trying to use client hooks | Add 'use client' directive |
| "Module not found" | Missing package | npm install [package] |
| Form submits but nothing happens | Server action not connected or missing 'use server' |
Check action binding |
| "hydration mismatch" | Server/client HTML differs | Move dynamic content to client component |
| Page shows raw code/JSON | Missing page component or wrong export | Check default export |
| Styles not applying | Tailwind class not compiling or wrong class name | Check tailwind config, restart dev server |
| "ECONNREFUSED" on database | Supabase not configured or env vars missing | Check .env.local |
| Login redirect loop | Middleware misconfigured | Check middleware matcher |
| Image not showing | Wrong path or missing from public folder | Fix path or move image |
| Dev server won't start | Port in use or syntax error | Kill port, check last edit |
| "Cannot read properties of undefined" | Accessing data before it loads | Add loading/null check |
| Build fails | TypeScript error or missing import | Check the specific error line |
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.
- 12d ago First seen · 106 lines · 88 tokens per session scan A 7606fcac128f
unstuck is a skill published in the GitHub repository sso-ss/vibe-ship-it (12 stars, last pushed 5mo ago), licensed MIT. It adds 88 tokens to every session and 1,017 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
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.