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 noahrasheta/director --skill undogit clone --depth 1 https://github.com/noahrasheta/directorWrote 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/noahrasheta/director/undo)<a href="https://agentmods.dev/skills/noahrasheta/director/undo"><img src="https://agentmods.dev/badge/skills/noahrasheta/director/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/noahrasheta/director/undo"><img src="https://agentmods.dev/badge/skills/noahrasheta/director/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.00021 | $0.01389 |
| Opus 5.5 | $0.00008 | $0.00556 |
| Sonnet 5.5 | $0.00004 | $0.00278 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
director: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 1mo 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Director's undo command. Your job is to safely go back to before the last task Director completed. This gives the user a safety net -- they can experiment knowing they can always go back.
Read these references for tone and terminology:
reference/plain-language-guide.md-- how to communicate with the userreference/terminology.md-- words to use and avoid
Follow all 7 steps below IN ORDER.
Step 1: Check for a project
Check if .director/ exists.
If it does NOT exist:
"Nothing to undo -- no project set up yet."
Stop here.
Step 2: Check for saved changes to undo
Run:
git log --oneline -1 2>/dev/null
If no output is returned (no history exists):
"Nothing to undo -- no progress has been saved yet."
Stop here.
Step 3: Identify the saved change
Parse the most recent entry from git log --oneline -1. Read the message to determine whether it was made by Director.
Director-made changes
These are changes Director created during normal workflow:
- Task changes: Plain-language descriptions from the build workflow (e.g., "Build the login page with form validation", "Add user settings page with profile editing")
- Quick changes: Start with
[quick]prefix (e.g., "[quick] Change button color to blue", "[quick] Fix typo on About page")
Non-Director changes
Everything else was NOT made by Director:
- Undo bookkeeping: Starts with "Log undo:" -- these are undo's own records, treat as non-Director
- Developer-style messages: Conventional prefixes like "fix:", "feat:", "chore:", "refactor:", "docs:", "style:", "test:", "perf:", "ci:", "build:", "wip:", "WIP"
- Generic messages: "update", "initial commit", "misc changes", "save progress", or any other message that does not match Director's patterns
If the change was NOT made by Director
Warn the user:
"The last saved change wasn't made by Director -- it looks like something you did manually. Still want to undo it?"
Wait for the user's response. If they decline, stop. If they confirm, continue to Step 4.
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.
- 1mo ago First seen · 169 lines · 21 tokens per session scan A 7a682cbcdc9d
director:undo is a skill published in the GitHub repository noahrasheta/director (2 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 1,389 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-inbox
Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
gsd-workspace
Manage GSD workspaces — create, list, or remove isolated workspace environments.
gsd-audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.