What is omniscitus-uninstall?

A cleanup tool that reverses changes made by Omniscitus Migrate, then removes Omniscitus project files.

Use it before uninstalling the Omniscitus plugin. It checks the migration record and removes, restores, or reverts each recorded change.

It helps restore the project to its earlier state when you want to remove Omniscitus. It uses a recorded change list so cleanup is limited to files previously changed by migration.

omniscitus-uninstall — Skill for Claude Code by DanialDaeHyunNam

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add DanialDaeHyunNam/omniscitus

Claude Code

/plugin install omniscitus

Made for: Claude Code.

Or install omniscitus, the plugin that ships this one along with the rest of its 16 skills, 3 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/omniscitus-uninstall/github.svg)](https://agentmods.dev/skills/danialdaehyunnam/omniscitus/omniscitus-uninstall)

Your own site

<a href="https://agentmods.dev/skills/danialdaehyunnam/omniscitus/omniscitus-uninstall"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/omniscitus-uninstall/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/danialdaehyunnam/omniscitus/omniscitus-uninstall"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/omniscitus-uninstall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,338 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00086	$0.01338
Opus 5	$0.00043	$0.00669
Sonnet 5	$0.00017	$0.00268
Haiku 4.5	$0.00009	$0.00134

Measured 12d ago against content hash 820572c1a40d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

omniscitus-uninstall scanned grade C with 1 finding 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 12d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

Manual cleanup: rm -rf .omniscitus and review CLAUDE.md for any omniscitus blocks.

plugins/omniscitus/skills/omniscitus-uninstall/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Omniscitus Uninstall — Surgical Removal

Reverse the file changes that /omniscitus-migrate made outside .omniscitus/, then remove .omniscitus/ itself. After this, /plugin uninstall omniscitus removes the plugin code and the project is back to a pre-omniscitus state.

This is the safe-uninstall counterpart to /omniscitus-migrate's anchor recording (see .omniscitus/migrate/anchor.yaml). Because Claude Code has no plugin-uninstall lifecycle hook, this skill must be run before /plugin uninstall.

When to Use

User types /omniscitus-uninstall
User says "omniscitus 제거", "uninstall omniscitus", "remove all omniscitus changes"
Use before /plugin uninstall omniscitus, never after

Instructions

Step 1: Verify anchor exists

Check .omniscitus/migrate/anchor.yaml. If missing:

⚠️ No anchor.yaml found at .omniscitus/migrate/anchor.yaml.
Either /omniscitus-migrate never ran, or this is a manually-set-up project.
Manual cleanup: rm -rf .omniscitus and review CLAUDE.md for any omniscitus blocks.

Stop.

Step 2: Show status (read-only)

node "${CLAUDE_PLUGIN_ROOT}/scripts/uninstall.cjs" status "$(pwd)"

This prints the anchor SHA + branch + footprint count + per-action breakdown. Relay the output to the user so they understand the scope.

Step 3: Show dry-run plan

node "${CLAUDE_PLUGIN_ROOT}/scripts/uninstall.cjs" dry-run "$(pwd)"

For each footprint entry, the script classifies what the reversal will be:

remove-section — surgical marker-based removal (for appended actions). Only the omniscitus-injected section is touched; user content elsewhere in the file is preserved.
git-checkout — whole-file restore from the anchor SHA (for modified actions). Loses any post-migration edits to the same file. The dry-run output flags this so the user can decide.
delete — removes the file (for created actions).
restore — git-checkout from anchor (for deleted actions).
skip — entry is already in the target state (file gone, marker missing, etc.).
warn — can't reverse (anchor SHA unreachable, marker not recorded, etc.). Listed so the user can handle manually.

Read the full file on GitHub · 135 lines

Changes

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.

12d ago First seen · 135 lines · 86 tokens per session scan C 820572c1a40d

Subscribe to this mod's changes

omniscitus-uninstall is a skill published in the GitHub repository DanialDaeHyunNam/omniscitus (5 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,338 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

omniscitus-uninstall