Skip to content
TakoAPI
Back to skills

mirage-proxy

by chandika

Web & Frontend Development
381Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Install and configure mirage-proxy as a transparent PII/secrets filter for OpenClaw LLM API calls.

Description

What This Skill Does

mirage-proxy sits between OpenClaw and LLM providers, intercepting API calls to redact secrets and PII before they reach the model. It replaces sensitive values with plausible fakes so the LLM processes realistic-looking but sanitized data. A bundled setup script handles binary download, proxy startup, and provider config patching.

Unlike per-agent prompt sanitization, mirage-proxy intercepts all LLM traffic at the network layer without requiring changes to any agent code.

When to Use It

  • Reviewing codebases that contain hardcoded API keys or credentials
  • Feeding customer records to an LLM without exposing real names or emails
  • Debugging agent prompts that pull values from environment variables
  • Comparing filtered vs unfiltered model responses side-by-side using model aliases
  • Running compliance-sensitive workflows where secrets must not leave the system unredacted

Example Workflow

INPUT

User asks an agent to review a .env file containing AWS access keys

AGENT
  1. 1

    Agent sends file contents in a prompt routed through the mirage-anthropic provider

  2. 2

    Proxy intercepts the outbound request and detects the AWS Access Key pattern

  3. 3

    Proxy replaces the real key with a plausible fake before forwarding to Anthropic

  4. 4

    LLM receives and processes the sanitized prompt

  5. 5

    Agent returns the response; real credentials were never transmitted

OUTPUT

LLM analysis of the config file with no real secrets exposed in transit

Installation

clawhub install chandika/mirage-proxy

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links