Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Add SHA256 binary verification
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
Here's how your AI assistant might use this skill in practice.
User asks an agent to review a .env file containing AWS access keys
- 1Agent sends file contents in a prompt routed through the mirage-anthropic provider
- 2Proxy intercepts the outbound request and detects the AWS Access Key pattern
- 3Proxy replaces the real key with a plausible fake before forwarding to Anthropic
- 4LLM receives and processes the sanitized prompt
- 5Agent returns the response; real credentials were never transmitted
LLM analysis of the config file with no real secrets exposed in transit