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/madappgang/claude-code/revertgit clone --depth 1 https://github.com/MadAppGang/claude-codeWhat 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.00015 | $0.01788 |
| Opus 5 | $0.00008 | $0.00894 |
| Sonnet 5 | $0.00003 | $0.00358 |
| Haiku 4.5 | $0.00002 | $0.00179 |
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 3d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<user_request> $ARGUMENTS </user_request>
**Before starting**, create todo list with these 5 phases:
1. Scope Selection - Identify what to revert (track/phase/task)
2. Impact Analysis - Find commits, files, status changes
3. User Confirmation - Present impact and get approval
4. Execution - Create revert commits and update files
5. Validation - Verify consistency and report results
**Update continuously**:
- Mark "in_progress" when starting each phase
- Mark "completed" immediately after finishing
- Keep only ONE phase "in_progress" at a time
</todowrite_requirement>
<confirmation_required>
ALWAYS require explicit user confirmation before:
- Reverting any commits
- Modifying plan.md status
- Deleting track files
Show exactly what will be changed BEFORE doing it.
</confirmation_required>
<non_destructive_default>
Default to creating revert commits, not force-pushing.
Preserve git history unless user explicitly requests otherwise.
</non_destructive_default>
<state_validation>
After any revert:
1. Verify plan.md matches git state
2. Verify metadata.json is consistent
3. Run project quality checks
4. Report any inconsistencies
</state_validation>
</critical_constraints>
<core_principles> Revert by logical units (track/phase/task), not raw commits. A task might have multiple commits - revert them together.
<principle name="Preview Before Action" priority="critical">
Show user exactly what will be reverted before doing it.
List commits, files, status changes.
</principle>
<principle name="Graceful Degradation" priority="high">
If full revert fails, offer partial revert options.
Never leave project in inconsistent state.
</principle>
</core_principles>
<phase number="2" name="Impact Analysis">
<step>Read metadata.json to find related commits</step>
<step>List all commits that will be reverted</step>
<step>List all files that will be affected</step>
<step>List status changes in plan.md</step>
</phase>
<phase number="3" name="User Confirmation">
<step>Present impact analysis to user</step>
<step>Ask for explicit confirmation</step>
<step>If declined, abort with no changes</step>
</phase>
<phase number="4" name="Execution">
<step>Create revert commits for each original commit</step>
<step>Update plan.md statuses back to [ ]</step>
<step>Update metadata.json to reflect revert</step>
<step>Remove completed tasks from history</step>
</phase>
<phase number="5" name="Validation">
<step>Verify git state matches plan.md</step>
<step>Run project quality checks</step>
<step>Report final state to user</step>
</phase>
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.
- 3d ago First seen · 239 lines · 15 tokens per session scan A fd1986e896d3
revert is a command published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 1,788 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-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.