obliteratus

Ablate refusal-encoding directions from open-weight LLM weights via CLI.

4|Updated May 18, 2026
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill obliteratus-zardli1115
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obliteratus
Source: https://github.com/ZardLi1115/zedclaw/tree/main/skills/mlops/inference/obliteratus
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill obliteratus-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps reduce or eliminate refusal/guardrail behaviors in open-weight LLMs by ablating the internal directions associated with refusal, without retraining or conventional fine-tuning.

Core Features & Use Cases

  • Refusal-direction removal: Projects out refusal-related activations from model weights using diff-in-means, SVD, LEACE, and related mechanistic interpretability techniques.
  • Multi-method workflow: Provides multiple CLI methods (e.g., advanced, aggressive, surgical, nuclear) and direction-extraction modes to match different model behaviors (standard dense vs. MoE vs. reasoning-heavy).
  • Verification & evaluation loop: Benchmarks refusal rate and checks coherence signals (e.g., perplexity/KL) to detect incomplete removal or quality damage.
  • Tunable execution: Supports hardware tiers, quantization options, interactive setup, web UI, and reusable YAML configs for reproducible runs.

Quick Start

Ask it to ablate refusals in meta-llama/Llama-3.1-8B-Instruct with the default recommended method and save the output model to ./abliterated-models by running: obliteratus obliterate meta-llama/Llama-3.1-8B-Instruct --method advanced --output-dir ./abliterated-models

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 open-weight LLM without retraining?

Remove LLM refusals by ablating refusal-encoding directions from model weights using mechanistic interpretability techniques. This weight surgery approach projects out refusal-related activations without conventional fine-tuning, directly modifying the model's internal representations.

What methods are available for ablating refusal directions in dense versus MoE models?

Ablation methods include advanced, aggressive, surgical, and nuclear CLI modes with direction-extraction techniques like diff-in-means, SVD, and LEACE. These modes match different model behaviors across standard dense, MoE, and reasoning-heavy architectures.

Can I verify model coherence and refusal rate after ablating guardrails?

You can verify refusal rate and coherence after ablating guardrails using the built-in evaluation loop. It benchmarks refusal frequency and checks perplexity or KL divergence signals to detect incomplete removal or quality damage.

Does obliteratus support quantized models and configurable hardware tiers?

Obliteratus supports quantization options, configurable hardware tiers, and reusable YAML configs for reproducible runs. It relies on torch, transformers, bitsandbytes, and accelerate to manage execution across different compute environments.

Why does my LLM still refuse requests after applying weight surgery?

Incomplete refusal removal after weight surgery indicates the chosen ablation method did not fully project out the refusal-encoding directions. Switching to a more aggressive CLI method or alternate direction-extraction mode may resolve the residual guardrails.

What are the limitations of using SVD ablation for LLM alignment?

SVD ablation for LLM alignment risks degrading model coherence if refusal-encoding directions overlap with general representation subspaces. Monitoring perplexity and KL divergence metrics is essential to catch quality damage during the ablation process.