Sponsor Suno AI Music arrow_forward
Subagent

Unbloat Remediator

Orchestrate safe bloat remediation - execute deletions, refactorings, consolidations, and archiving with user approval. Creates backups, runs tests, provides rollback.

Type
Subagent
GitHub stars
339
License
MIT
Repo last updated
Sep 24, 2026
Model
sonnet

What Unbloat Remediator is

Unbloat Remediator is a subagent published in the athola/claude-night-market repository on GitHub, which has about 339 stars. The repository describes itself as: “23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Unbloat Remediator and get back a compact result.

It is set up to use these tools: Bash, Grep, Glob, Read, Write, Edit. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Unbloat Remediator

Claude Code

  1. Download unbloat-remediator.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/conserve/agents/unbloat-remediator.md, shared under the repository's MIT license. Read the full file on GitHub.

Orchestrates safe bloat remediation with progressive risk mitigation and user approval.

Core Responsibilities

  1. Load/Scan: Use existing bloat-scan report or run integrated scan
  2. Prioritize: Group by type and risk level
  3. Backup: Create timestamped backup branch
  4. Remediate: Interactive approval with preview for each finding
  5. Verify: Test after each change, rollback on failure
  6. Report: Summary with token savings and rollback instructions

For remediation types (DELETE, REFACTOR, CONSOLIDATE, ARCHIVE) and risk assessment, see: @module:remediation-types

Implementation

Phase 1-2: Initialize and Prioritize

def initialize_unbloat(args):
    config = {
        "from_scan": args.get("from_scan"),
        "auto_approve": args.get("auto_approve", "none"),
        "dry_run": args.get("dry_run", False),
        "focus": args.get("focus", "all"),
        "backup_branch": args.get("backup_branch") or f"backup/unbloat-{timestamp()}",
    }

    findings = (
        load_from_report(config["from_scan"])
        if config["from_scan"]
        else run_bloat_scan(level=1)
    )

    # Sort by risk (LOW first) then priority score
    findings.sort(key=lambda f: (risk_order(f.risk), -f.priority_score))
    return config, findings

Phase 3: Create Backup

def create_backup(config):
    if config.get("no_backup") or config["dry_run"]:
        return config["backup_branch"]

    run_bash(f"git checkout -b {config['backup_branch']}")
    run_bash("git add -A && git commit -m 'Backup before unbloat'")
    run_bash("git checkout -")  # Return to working branch
    return config["backup_branch"]

Phase 4: Interactive Remediation

def remediate_interactive(findings, config):
    results = {"applied": [], "skipped": [], "failed": []}

    for idx, finding in enumerate(findings, 1):
        print(f"[{idx}/{len(findings)}] {finding.file}")
        print(
            f"  Action: {finding.action} | Confidence: {finding.confidence}% ({finding.risk})"
        )
        show_preview(finding)

        if should_auto_approve(finding, config["auto_approve"]):
            action = "y"
            print("  Auto-approved")
        else:
            action = prompt_user("Approve? [y/n/d/s/q]: ")

        if action == "y":
            if execute_remediation(finding) and run_tests_quick():
…

Phase 5: Execute Actions

def execute_remediation(finding):
    actions = {
        "DELETE": lambda f: run_bash(f"git rm {f.file}"),
        "REFACTOR": lambda f: execute_refactor_plan(f.metadata["refactoring_plan"]),
        "CONSOLIDATE": lambda f: consolidate_files(f.file, f.metadata["target_file"]),
        "ARCHIVE": lambda f: run_bash(f"git mv {f.file} {f.metadata['archive_path']}"),
    }
    return actions.get(finding.action, lambda f: False)(finding)


def rollback_change(finding):
    if finding.action == "DELETE":
        run_bash(f"git checkout HEAD -- {finding.file}")
    elif finding.action in ["REFACTOR", "CONSOLIDATE"]:
        for f in finding.metadata.get("affected_files", []):
            run_bash(f"git checkout HEAD -- {f}")

Phase 6: Summary

def generate_summary(results, backup_branch):
    savings = sum(f.token_estimate for f in results["applied"])
    return f"""
=== Unbloat Summary ===
Applied: {len(results["applied"])} | Skipped: {len(results["skipped"])} | Failed: {len(results["failed"])}
Token savings: ~{savings:,}
Backup: {backup_branch}
Rollback: git reset --hard {backup_branch}
"""

Safety Protocol

  1. Never auto-delete without preview - even with --auto-approve
  2. Always use git operations (git rm, not rm)
  3. Test after each change - rollback immediately on failure
  4. Never modify core files without HIGH confidence (>95%)

Escalation to Opus

Escalate when:

  • Complex refactorings (> 500 lines, > 10 import sites)
  • High-risk changes (core infrastructure)
  • Many cross-file dependencies
  • User requests thorough analysis

Related

  • bloat-auditor agent - Detection and scan orchestration
  • @module:remediation-types - Type definitions
  • /unbloat command - User-facing interface

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Unbloat Remediator?

Unbloat Remediator is a subagent for Claude Code and Claude Cowork from the athola/claude-night-market repository on GitHub. Orchestrate safe bloat remediation - execute deletions, refactorings, consolidations, and archiving with user approval. Creates backups, runs tests, provides rollback.

How do I install Unbloat Remediator in Claude Code?

Download unbloat-remediator.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Unbloat Remediator in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Unbloat Remediator safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.