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/5uck1ess/devkit/stucknpx skills add 5uck1ess/devkit --skill stuckgit clone --depth 1 https://github.com/5uck1ess/devkitWhat 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 | $0.00026 | $0.00503 |
| Opus 5 | $0.00013 | $0.00251 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
stuck 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stuck Detection & Recovery
Symptoms
You are stuck if any of these are true:
- Same error message appeared 2+ times in a row
- You reverted the same change twice
- The metric hasn't improved in 3+ iterations
- You're making changes that don't address the actual error
- You're adding complexity to work around a problem instead of fixing it
Recovery Protocol
0. Check the Scratchpad
Read .devkit/scratchpads/current.md first. It records what was already tried and why it failed. If the scratchpad shows 3+ failed iterations, skip straight to Step 5: Escalate — the pattern of failures is the diagnosis.
1. Stop and Diagnose
Don't retry the same approach. Read the error carefully:
- What is the actual error message?
- What file and line does it point to?
- Is this the same error as last iteration, or a new one?
2. Backtrack
If the last 2+ attempts failed:
- Revert to the last known-good state:
git checkout -- . - Re-read the original goal and the current state of the code
- The problem may be upstream of where you're looking
3. Simplify
Reduce scope:
- Fix one thing at a time, not three
- Remove the last thing you added and see if the base case works
- Use the simplest possible implementation, even if inelegant
4. Change Strategy
If the same approach failed twice:
- Try a fundamentally different approach, not a variation
- Read the docs or source of the library/API you're calling
- Check if the function signature or types changed
5. Escalate
If you've tried 3+ different approaches:
- Report what you've tried and what failed
- Show the exact error
- Ask the user for guidance — they may know something you don't
Anti-Patterns
- Retry loop — Running the same command hoping for a different result
- Shotgun debugging — Changing multiple things at once without understanding why
- Complexity spiral — Adding workarounds on top of workarounds
- Ignoring the error — Suppressing or catching exceptions instead of fixing the cause
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.
- 2d ago First seen · 64 lines · 26 tokens per session scan A 6c802f340085
stuck is a skill published in the GitHub repository 5uck1ess/devkit (5 stars, last pushed 13d ago), licensed MIT. It adds 26 tokens to every session and 503 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
dynamic-workflows
Ultracode / Max-Parallel mode — dynamic workflows fan work out across tens–hundreds of adversarially-verified parallel subagents for large, decomposable jobs (codebase-wide audits, big migrations, cross-checked research). Opt-in; higher token spend.
agent-teams
Experimental Agent Teams orchestration — run CCGodMode agents as parallel teammates with SharedTaskList coordination (requires CLAUDECODEEXPERIMENTALAGENTTEAMS=1).
cost-efficiency
Smart Routing — the DEFAULT CCGodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.
quality-gates
Parallel quality gate orchestration — @validator and @tester run simultaneously after @builder, with mandatory decision matrix for pass/fail routing.
sprint-planning
Plan-first orchestration (ADR-004): comprehensive PLAN.md, sprint files with write-scope ownership, preflight checks, serialized integration, and the release sprint. Use for any non-trivial or multi-part request BEFORE dispatching agents.
workflows
CCGodMode Full-Gates workflow definitions — used for high-risk work and when Smart Routing escalates. Default routing is Smart Routing (skills/cost-efficiency/).