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 nguyenthanhtat/screen1-claude --skill undogit clone --depth 1 https://github.com/nguyenthanhtat/screen1-claudeWrote 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/nguyenthanhtat/screen1-claude/undo)<a href="https://agentmods.dev/skills/nguyenthanhtat/screen1-claude/undo"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/undo/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/nguyenthanhtat/screen1-claude/undo"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/undo.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.00000 | $0.04452 |
| Opus 5 | $0.00000 | $0.02226 |
| Sonnet 5 | $0.00000 | $0.00890 |
| Haiku 4.5 | $0.00000 | $0.00445 |
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 8d 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 — 795 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Undo
Parent Skill: /git
Path: /git/undo
Purpose
Master undoing changes at every stage: unstage files, discard working changes, amend commits, reset history, revert safely, and recover lost commits with reflog.
When to Use
Trigger automatically when:
- User mentions: undo, reset, revert, restore, reflog, recover, amend, rollback
- Made mistake in commit
- Need to unstage files
- Want to discard changes
- Recover deleted commits
- Fix commit history
Chat commands:
/git/undo unstage this file
/git/undo discard my local changes
/git/undo fix my last commit message
/git/undo undo last commit but keep changes
/git/undo recover deleted commit
Requirements
Verification
# Check current state
git status
# See commit history
git log --oneline -5
# Check reflog (for recovery)
git reflog
Critical Rules
Undo Workflow
File States & Undo Commands:
Working Directory → Staging → Repository
(modified) (staged) (committed)
↓ ↓ ↓
git restore git restore git reset
--staged or git revert
Recovery: git reflog (for any deleted commits)
Patterns
Pattern 1: Unstage Files (Restore --staged)
Problem: Staged file by mistake
# ❌ BAD: Old confusing syntax
git reset HEAD file.js # Works but unclear
# ✅ GOOD: Modern, clear syntax (Git 2.23+)
git restore --staged file.js
# Unstage all files
git restore --staged .
# Unstage specific files
git restore --staged src/app.js src/utils.js
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.
- 8d ago First seen · 795 lines · 0 tokens per session scan A 5a7773808a6f
undo is a skill published in the GitHub repository nguyenthanhtat/screen1-claude (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,452 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-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…