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.
git clone --depth 1 https://github.com/madeinplutofabio/vibe-revertWrote 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/madeinplutofabio/vibe-revert/viberevert-setup)<a href="https://agentmods.dev/commands/madeinplutofabio/vibe-revert/viberevert-setup"><img src="https://agentmods.dev/badge/commands/madeinplutofabio/vibe-revert/viberevert-setup/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/commands/madeinplutofabio/vibe-revert/viberevert-setup"><img src="https://agentmods.dev/badge/commands/madeinplutofabio/vibe-revert/viberevert-setup.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.00022 | $0.00404 |
| Opus 5.5 | $0.00009 | $0.00162 |
| Sonnet 5.5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
viberevert-setup 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.
What it actually says
Enable VibeRevert for this project
Set up VibeRevert for the repository that is currently open, then confirm it worked.
Step 1: run the installer
Run this exact command in the root of the current project:
npx -y [email protected] install --cursor
On success it prints a line beginning with [applied: Cursor:.
If it prints [refused: ...] or [skipped: ...], stop and show the user that
line verbatim. Do not try to work around a refusal by editing files yourself.
Step 2: verify the result
Read .cursor/mcp.json in the project root and confirm it contains an
mcpServers.viberevert entry. Show the user its contents.
Step 3: tell the user how to activate it
Configuring the server and activating it are separate steps in Cursor. Tell the user to:
- Reload the window (
Developer: Reload Window) so Cursor picks up the new server. - Open Customize → MCP, find
viberevert, and enable it if Cursor shows it as disabled.
Once enabled, VibeRevert connects and exposes its 8 tools in this project.
Rules
- Only touch the project that is currently open.
- Do not modify any other Cursor configuration, including
~/.cursor/mcp.jsonor settings. - Do not hand-write
.cursor/mcp.json. The installer owns that file, keeps a recovery journal, and knows the correct platform-specific launch form. - If the project is not a Git repository, say so and stop. VibeRevert protects a Git working tree and has nothing to operate on otherwise.
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 Changed e5496435c086
- 1mo ago Changed 848e82da45b1
- 1mo ago First seen · 49 lines · 22 tokens per session scan A b6a964fedf76
viberevert-setup is a command published in the GitHub repository madeinplutofabio/vibe-revert (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 404 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 commands, from other repositories
constitution
A command for creating or updating a project's constitution, a document that records its governing principles and working rules, in Simplified Chinese.
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].
contract-signoff
Harden the current decision set into a normative source of truth with no residual ambiguity, saved in DECISIONS.md and TASKSTATE.md as reviewable edits. Use when decisions are resolved, the contract direction is stable, and wording needs hardening before planning or implementation. Do not use when major ambiguities…
code-locate
Locate code paths and line ranges for a described behavior: up to 10 candidates with HIGH/MEDIUM/LOW confidence and a search trail, plus a proposed SOURCEOFTRUTH.md update. Use when the first question is where one specific behavior lives and paths are unknown. Do not use when paths are explicit, the codebase is tiny…
harvest-session-learnings
Scan the session and task artifacts for reusable lessons (what was tried, what failed and why, what surprised us) and propose entries to append to LEARNINGS.md, the produce-side counterpart to what task-init reads. Use on demand mid-task after a hard-won fix or surprising failure, or at closure to sweep a long…
screen-spec
Generate a screen specification from a Figma frame using MCP tools (getdesigncontext, getscreenshot), matching the SCREENSPEC.md template (layout, states). Use when documenting a specific screen. Do not use when the screen has no Figma frame or the spec already exists, for 6 or more screens (use screen-spec-fleet), or…