obliteratus

Remove refusal behaviors from LLMs using mechanistic interpretability techniques.

Updated May 8, 2026
One-click install
npx skills add https://github.com/gztcode/my-skills --skill obliteratus-gztcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obliteratus
Source: https://github.com/gztcode/my-skills/tree/main/obliteratus
Command: npx skills add https://github.com/gztcode/my-skills --skill obliteratus-gztcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires obliteratus, torch, transformers, bitsandbytes, accelerate, safetensors, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the issue of refusal behaviors in LLMs, allowing for the removal of guardrails while preserving reasoning and performance.

Core Features & Use Cases

  • Refusal Removal: Removes guardrails from LLMs to eliminate refusal behaviors.
  • Mechanistic Interpretability: Uses techniques like diff-in-means, SVD, and LEACE to surgically remove refusal directions.
  • CLI Methods & Analysis Modules: Offers a suite of CLI methods and analysis modules for detailed evaluation and refinement.
  • Use Case: If you have an LLM that is refusing to generate certain types of responses, you can use this Skill to remove those refusal behaviors.

Quick Start

Run the obliteratus obliterate <model_name> --method advanced --output-dir ./abliterated-models command to remove refusal behaviors from your LLM model.

Frequently Asked Questions about obliteratus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove refusal behaviors from an LLM?

To remove refusal behaviors from an LLM, use mechanistic interpretability techniques like diff-in-means, SVD, and LEACE to surgically remove refusal directions while preserving reasoning. This process applies directly to fine-tuning and retraining workflows.

What is the best way to remove guardrails from a model without losing reasoning performance?

Removing guardrails from a model without losing reasoning performance is achieved by applying model surgery techniques that target and eliminate specific refusal directions. This approach preserves the underlying reasoning capabilities while eliminating refusal behaviors.

Do I need specific Python libraries to remove refusal directions from my model?

Yes, removing refusal directions requires torch, transformers, bitsandbytes, accelerate, and safetensors for execution. These dependencies provide the necessary environment for applying mechanistic interpretability and model surgery techniques.

How does mechanistic interpretability work for eliminating LLM guardrails?

Mechanistic interpretability eliminates LLM guardrails by using analysis modules and methods like diff-in-means, SVD, and LEACE to identify and surgically remove refusal directions. This allows for detailed evaluation and refinement of the model.

Can I use CLI commands to remove guardrails from my LLM?

Yes, you can remove guardrails from your LLM using CLI methods by running the obliterate command with your model name and an advanced method flag. This outputs the modified model to a specified directory for evaluation.

When should I not use model surgery to remove LLM guardrails?

You should avoid using model surgery to remove LLM guardrails if your environment lacks torch, transformers, bitsandbytes, accelerate, and safetensors. These dependencies are strictly required for the execution of refusal removal techniques.