The all-in-one mod pack for Claude Code: usage limits and the context window right above the prompt, a guard with undo for rm -rf and git reset --hard, .env files and secrets kept out of the model, and a receipt under every answer.
Install
claude plugin install ultramod --marketplace mertkayacs/ultramod135 downloadsnpm registry (npm, Yarn, pnpm, Bun): 86 · Claude Code marketplace: 49 · as of October 10, 2026
Four mods do most of the work. Everything else is a smaller variation on the same idea.
A row above the prompt with a context bar, both rate-limit windows and their reset times, the live turn time, session cost, model and set. When the terminal narrows, the limits shorten first and whole segments drop from the end instead of wrapping.
Files changed, commands run, tests and builds with pass or fail, time and cost, in one line. When the answer claims tests pass and no test ran after the last edit, the receipt adds unverified: says tests pass, no passing test run after the last edit.
Recursive rm outside the safe folders, git reset --hard, force push, drop table, terraform destroy: the command stops and asks. In a git work tree, Ultra Mod first tries to save a snapshot of the work tree, untracked files included, so /ultra undo can bring it back. Snapshots are best effort, and a restore never deletes a file.
Reads of .env files, private keys and credential files are blocked, shell commands that would print them are refused, and tokens in output are replaced with a marker such as [redacted:private-key] before the text is stored.
One plugin, three jobs. Flip any of them off in the control pane without leaving the set.
What is happening, while it happens.
The things worth a second of friction.
Where a long session usually goes wrong.
.claude/pins.md in the system prompt for the whole session.A set is a named combination of mod modes. Pick one and every mod moves with it.
essentialsdefault
The default for everyday work. Context on screen, receipts when tools run, a question before anything destructive.
strict
Team repositories and production code. A receipt on every turn, a longer risk table, tidy asks before new files.
flow
Fewest interruptions. Compact HUD, receipts only when something failed, no chime.
marathon
Long unattended runs. Guard refuses risky commands and notifies, tests refuse weakening, compaction at 88 percent.
quiet
Same safety, nothing on screen. HUD and receipts off, guard and secrets still running.
/ultra set saves the choice for the current project folder and reloads the mods live. Flip any mod inside /ultra and the set shows as essentials* with an asterisk; /ultra reset drops those overrides.
/ultra set strictEvery claim below is checkable in a clone of the repository.
No mod makes a request. The validator reports the plugin's hooks and calls, and none of them reach the network.
Nothing is measured or sent. Session state stays in Claude Code's own store, under keys that start with ultramod.
Hooks load TypeScript files directly. The npm installer is a single script that prints every command before it runs it.
A broken guard refuses the command. A broken HUD returns the next hook in the chain and never blocks a tool call.
The command below lists every event the plugin hooks and every call it makes, including the line env writes: nothing.
claude plugin validate ./pluginCurrent version 1.0.3. Requires Claude Code 2.1.287 or later.
One command from any terminal. It adds the marketplace and installs the plugin.
claude plugin install ultramod --marketplace mertkayacs/ultramodThe same command inside a session. The mods start right away.
/plugin install ultramod --marketplace mertkayacs/ultramodAdd the marketplace first, then install from it.
claude plugin marketplace add mertkayacs/ultramod
claude plugin install ultramod@ultramodChecks your Claude Code version and prints each command before running it.
npx ultramodThen open Claude Code and run /ultra
If Claude Code says the plugin is not found in any configured marketplace, add the marketplace first with: claude plugin marketplace add mertkayacs/ultramod
The all-in-one mod pack for Claude Code. One plugin holds ten mods that run as hooks: a HUD for usage limits and the context window, receipts for every turn, a guard with undo for risky commands, secret protection, test integrity, notifications, auto-compaction, loop breaking, pinned rules and documentation tidying. A set switches them all at once.
claude -p or the SDK?Hooks run everywhere a plugin loads. The HUD and the control pane are drawn only in the terminal and the Desktop app; VS Code chat, claude -p and the SDK run the hooks without drawing.
No. Mods run with your permissions, so claude plugin validate is the audit: it lists every hook and every call. docs/security.md holds the full table.
No network calls, no telemetry, no runtime dependencies. The validator confirms env writes: nothing.
/ultra set with a name: essentials, strict, flow, marathon or quiet. The choice is saved per project. Open /ultra to flip single mods, and run /ultra reset to drop the overrides.
If an answer says tests pass, the build succeeds or the type check passes, and no matching command ran after the last edit in that turn, the receipt adds unverified: says tests pass, no passing test run after the last edit. It never blocks the turn.