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 commands/danielpodolsky/ownyourcode/stuckgit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWhat 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.00009 | $0.01838 |
| Opus 5 | $0.00005 | $0.00919 |
| Sonnet 5 | $0.00002 | $0.00368 |
| Haiku 4.5 | $0.00001 | $0.00184 |
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 yesterday.
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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/own:stuck
⚠️ PLAN MODE WARNING: Toggle plan mode off before running this command (
shift+tab). OwnYourCode commands don't work correctly with plan mode.
Guide the user through systematic debugging using Protocol D.
Protocol D: The Stuck Framework
This is how seniors debug. They don't panic. They systematically narrow down.
The 5 Steps:
- READ — Read the error out loud. Word by word. What is it saying?
- ISOLATE — Where exactly is the failure? Frontend? Backend? Network?
- DOCS — What does the documentation say about this error?
- HYPOTHESIZE — Based on that, what do you think the fix might be?
- VERIFY — Try it. Did it work? Why or why not?
Why This Matters
Most juniors see an error and immediately:
- Google the exact error message
- Copy the first Stack Overflow answer
- Try random things until something works
This creates dependency, not skill.
Seniors:
- Read the error carefully
- Understand what it's telling them
- Narrow down the search space
- Verify against documentation
- Fix with understanding
Protocol D builds the senior debugging habit.
Execution Flow
Step 1: READ the Error
Start with this exact prompt:
"Read the error message out loud. Word by word. What is it actually saying?
Don't Google it yet — just read what it says."
Use AskUserQuestion to structure this:
Question: "What type of issue are you facing?"
Options:
1. Error message in console/terminal
Description: There's a specific error I can share
2. Unexpected behavior (no error)
Description: It's not doing what I expect but no error
3. Build/compilation failure
Description: Code won't build or compile
4. Test failure
Description: Tests are failing
Then:
"Paste the FULL error message here (not just part of it)."
After they paste, ask them to interpret:
"In your own words, what is this error telling you? Don't search for solutions yet — what is the error literally saying?"
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.
- yesterday First seen · 291 lines · 9 tokens per session scan A 8857a4a50fb1
stuck is a command published in the GitHub repository DanielPodolsky/ownyourcode (276 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 1,838 once invoked, about $0.0000 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.
Other commands, from other repositories
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
version
Display current guide and Claude Code versions.
toh-help
Display all Toh Framework commands and quick usage guide.
diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.
start
Start Forge Mentor in this project — connect accounts, agree permissions, and begin the foundation interrogation.