CLI & API

AI tool integration

Place the following skill file at ~/.claude/skills/mimicry/SKILL.md, and Claude Code automatically calls the mimicry CLI to analyze traffic when you ask about HTTP traffic.

Requests like "find out which APIs are being called," "find requests returning 404," or "create a mock for this domain" automatically trigger the skill. Other AI coding tools can drive it the same way via the REST API / CLI.

---
name: mimicry
description: >
  Operate the Mimicry HTTP/HTTPS proxy tool via the CLI.
  Automate traffic inspection and analysis, mock rule generation, and log saving during iOS/Android app development.
  Actively use this skill for requests about HTTP traffic or proxy logs, such as
  "check the traffic in Mimicry", "find out which APIs are being called", "create a mock from the logs",
  "show me the response body", "what are the endpoints for this domain?", "investigate requests returning 404", and so on.
  Apply it to investigation requests about an app's traffic, API responses, and network logs
  even when the user does not explicitly say "Mimicry".
user-invocable: false
---

# Mimicry CLI Guide

Mimicry is a proxy tool that captures HTTP/HTTPS traffic while an app is running.
Using the CLI (`mimicry`), you can automate traffic inspection, log search, and mock generation without touching the GUI.

**Prerequisite**: The Mimicry GUI app must already be running.
If it is not running, prompt to start it with `open -a Mimicry` before proceeding.

## Command reference

```bash
# Status & overview
mimicry status                              # Check proxy status and log count
mimicry domains                             # List captured domains
mimicry endpoints <domain>                  # List endpoints for a specific domain

# Log search
mimicry logs                                # List the 50 most recent entries
mimicry logs --domain <domain>              # Filter by domain
mimicry logs --method POST --limit 20       # Filter by HTTP method
mimicry logs --status-code 404              # Filter by status code
mimicry logs --url "*/users/*"              # Filter by URL pattern (glob)
mimicry logs clear                          # Clear all logs

# Inspect details (use an ID from logs)
mimicry log <id>                            # Request/response headers and details
mimicry log <id> --body                     # Show the response body

# Save & generate mocks
mimicry save <output-path>.har              # Save logs to a .har file
mimicry save <output-path>.har --domain <domain>
mimicry mock                                # Generate mock rules from all logs
mimicry mock --domain <domain>              # Generate mock rules for one domain

# Generate a curl command
mimicry curl <id>                           # Output a curl command that reproduces the request

# Extra log options
mimicry logs --watch                        # Tail new logs (tail -f mode)
mimicry logs --reverse                      # Show in oldest-first order
mimicry logs --count-only                   # Output the count only
mimicry logs --fields method,status,url     # Select output fields

# Extra recording commands
mimicry recording list-devices              # List recordable devices
mimicry recording start --video-device <id> # Record with screen capture
mimicry recording status                    # Check recording status
mimicry recording show <id>                 # Recording details
mimicry recording delete <id>               # Delete a recording
mimicry recording playback-status           # Check playback status

# Shell completion
mimicry completions <shell>                 # Generate a shell completion script (bash/zsh/fish)

# Standalone server
mimicry serve --rules <file> [options]      # Start a proxy server without the GUI
```

## Workflows by goal

### Get an overview of all traffic

```bash
mimicry status
mimicry domains
mimicry endpoints <domain>
```

### Inspect an API response

```bash
mimicry logs --domain <domain> --limit 10
mimicry log <id>
mimicry log <id> --body
```

### Track down errors

```bash
mimicry logs --status-code 500
mimicry logs --url "*/auth/*" --status-code 401
```

### Create a mock for testing

```bash
mimicry mock --domain <domain>
# → Import the generated file into the Mimicry GUI
```

## Troubleshooting

| Symptom | Fix |
|------|------|
| Cannot connect to Mimicry app. | Start it with `open -a Mimicry` |
| No logs (0 entries) | Interact with the app, then retry |
| The specified ID is not found | Check the latest ID with `mimicry logs` |