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/owainlewis/youtube-tutorials/undogit clone --depth 1 https://github.com/owainlewis/youtube-tutorialsWhat 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.00000 | $0.00314 |
| Opus 5 | $0.00000 | $0.00157 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
undo 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.
What it actually says
Undo
Undo a recent git mistake safely.
What happened?
$ARGUMENTS — describe the mistake (e.g. "committed to main by accident", "undo last commit", "wrong files got committed")
Common scenarios
Undo last commit, keep the changes
git reset --soft HEAD~1
Changes go back to staging. Nothing lost.
Undo last commit, unstage the changes
git reset HEAD~1
Changes stay in working directory but are unstaged.
Accidentally committed to main
- Create a new branch from current state
- Switch back to main
- Reset main to before the commit
- Push the changes on the new branch instead
Wrong files got committed
git reset --soft HEAD~1to undo the commit- Unstage the wrong files
- Re-commit with only the correct files
Need to recover something lost
- Check
git reflogto find the state you want - Explain each reflog entry in plain language
- Ask before taking any action
Rules
- Always explain what will happen before running destructive commands
- Prefer
--softover--hardto preserve work - Never run
git reset --hardwithout explicit confirmation - If changes have been pushed, use
git revertinstead ofgit reset - Check
git stash list— the user might have stashed work they forgot about
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 · 46 lines · 0 tokens per session scan A 653cfbb955a8
undo is a command published in the GitHub repository owainlewis/youtube-tutorials (365 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 314 tokens. 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
workflow-claude-settings
Track Claude Code settings report changes and find what needs updating.
development-workflows
Update the DEVELOPMENT WORKFLOWS table by researching all 11 workflow repos in parallel.
implement
Execute phased implementation with validation gates.
plan
Create comprehensive planning documentation for a feature.
research
Research and analyze feature viability - GO/NO-GO decision gate.
workflow-claude-commands
Track Claude Code commands report changes and find what needs updating.