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/hoshikitsunoda/figma-plugins-vibe-coding-template/undo-changesgit clone --depth 1 https://github.com/hoshikitsunoda/figma-plugins-vibe-coding-templateWrote 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/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/undo-changes)<a href="https://agentmods.dev/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/undo-changes"><img src="https://agentmods.dev/badge/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/undo-changes.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00262 |
| Opus 5 | $0.00000 | $0.00131 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
undo-changes 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 4d 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.
What it actually says
Discards uncommitted changes safely.
What it does:
- Shows what changes will be discarded
- Asks for confirmation before proceeding
- Reverts all uncommitted changes to last commit state
Usage: /undo_changes
Important: This cannot be undone. Discarded changes are permanently lost.
Steps
-
Check for changes
- Run
git status --porcelain - If no changes, tell user: "No uncommitted changes to undo."
- Stop here if nothing to undo
- Run
-
Show what will be discarded
- Run
git statusto show changed files - Run
git diff --statto show a summary of changes - List the files that will be affected
- Run
-
Ask for confirmation
- Warn: "This will permanently discard all uncommitted changes. This cannot be undone."
- Ask: "Are you sure you want to discard these changes?"
- If user says no, stop here
-
Discard changes
- Run
git checkout -- .to discard modified files - Run
git clean -fdto remove untracked files - Confirm: "All uncommitted changes have been discarded."
- Run
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.
- 4d ago First seen · 35 lines · 0 tokens per session scan A c31c03e9a2b1
undo-changes is a command published in the GitHub repository hoshikitsunoda/figma-plugins-vibe-coding-template (21 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 262 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.