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/ddunnock/claude-plugins/revertgit clone --depth 1 https://github.com/ddunnock/claude-pluginsWhat 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.00008 | $0.00787 |
| Opus 5 | $0.00004 | $0.00394 |
| Sonnet 5 | $0.00002 | $0.00157 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
revert 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revert
Revert to a previous git checkpoint with failure analysis and artifact recommendations.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Usage
/revert # Revert to most recent checkpoint
/revert [checkpoint-tag] # Revert to specific checkpoint
/revert --list # List available checkpoints
/revert --dry-run # Preview without executing
MANDATORY: Pre-Revert Hooks
Pre-Hook 1: List and Validate Checkpoints
# List speckit checkpoints
git tag -l "speckit-checkpoint-*" --sort=-creatordate
IF no checkpoints exist: Stop and inform user.
Pre-Hook 2: Show Revert Preview
Before reverting, show:
- Files that will be reverted
- Tasks that will be reset
- Changes that will be lost
Get explicit confirmation before proceeding.
Revert Process
Step 1: Save Current State for Analysis
# Save diff for analysis
git diff HEAD [checkpoint] > .claude/.cache/failed-changes.diff
# Save commit log
git log --oneline [checkpoint]..HEAD > .claude/.cache/failed-commits.log
Step 2: Execute Revert
# Stash uncommitted changes
git stash push -m "speckit-pre-revert-$(date +%Y%m%d_%H%M%S)"
# Reset to checkpoint
git reset --hard [checkpoint]
MANDATORY: Post-Revert Failure Analysis
CRITICAL: Always analyze what went wrong after reverting.
Analysis Steps
-
Examine the diff - What was changed?
-
Identify failure category:
- SPEC_GAP - Requirements unclear
- APPROACH_WRONG - Need different architecture
- DEPENDENCY_ISSUE - External problem
- TEST_MISMATCH - Tests don't match reality
- SCOPE_CREEP - Too much at once
- KNOWLEDGE_GAP - Need more research
-
Generate recommendations:
- Spec clarifications needed?
- Plan revisions required?
- Task decomposition suggested?
Update Artifacts
- project-status.md - Log revert, add blocker
- tasks.md - Reset status, add failure notes
- Create failure report - speckit/failure-analysis-[date].md
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 · 148 lines · 8 tokens per session scan A fa24862f865f
revert is a command published in the GitHub repository ddunnock/claude-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 787 once invoked, about $0.0000 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-30.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.