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/latestaiagents/agent-skills/git-undogit clone --depth 1 https://github.com/latestaiagents/agent-skillsWhat 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.00016 | $0.00604 |
| Opus 5 | $0.00008 | $0.00302 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
git-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 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/git-undo
Recover from any Git mistake. Tell me what happened and I'll help you fix it.
What I Need From You
Describe what went wrong:
- "I accidentally committed to main"
- "I did a hard reset and lost my changes"
- "I force pushed and overwrote my colleague's work"
- "I deleted a branch with unmerged commits"
- "I rebased and now everything is messed up"
Recovery Workflow
Step 1: Assess the Situation
First, I'll check your current Git state:
# Current branch and status
git status
# Recent history
git log --oneline -10
# Reflog (your safety net)
git reflog -20
Step 2: Identify Recovery Path
Based on your situation, I'll recommend one of these recovery methods:
| Situation | Recovery Method |
|---|---|
| Committed to wrong branch | git cherry-pick or git reset --soft |
| Lost commits after reset | git reflog + git reset |
| Force push overwrote remote | git reflog + coordinate with team |
| Deleted branch | git reflog + git checkout -b |
| Bad rebase | git reflog + git reset --hard ORIG_HEAD |
| Accidentally staged files | git restore --staged |
| Want to undo last commit | git reset --soft HEAD~1 |
Step 3: Execute Recovery
I'll provide the exact commands with safety checks:
-
Create backup branch first (always)
git branch backup-$(date +%Y%m%d-%H%M%S) -
Execute recovery commands
-
Verify the fix worked
git log --oneline -5 git status
Common Scenarios
"I committed to main instead of my feature branch"
# Save the commit hash
COMMIT=$(git rev-parse HEAD)
# Reset main to before your commit
git reset --hard HEAD~1
# Switch to feature branch and apply commit
git checkout feature-branch
git cherry-pick $COMMIT
"I lost commits after git reset --hard"
# Find lost commits in reflog
git reflog
# Look for your commit message, then:
git reset --hard HEAD@{n} # n = number from reflog
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 · 103 lines · 16 tokens per session scan A 9d74701f5b1a
git-undo is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 604 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 commands, from other repositories
fw-setup-use
Workspace FDK stack switch — nvm use from .nvmrc or explicit 10/9 (Node 24.11 vs 18); optional --write-nvmrc and --global flags.
fdk-migrate
Migrate a legacy Freshworks app from platform-version 2.3 (2.x), FDK 9.x, and Node 18 to Platform 3.0 with FDK 10.0.1 and Node 24.11.0. Transforms manifest, request templates, Crayons UI, and validates on the new toolchain. Does not install fdk/Node—use fw-setup (or prompt user to add it) per SKILL.md.
fdk-fix
Fix all platform validation errors and lint errors in a Freshworks app. Runs fdk validate, identifies fatal errors and lint issues, applies fixes iteratively, and re-validates until all errors are resolved.
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
fw-setup-status
Check FDK and Node.js installation status (/fw-setup status); optional --verbose diagnostics.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.