proxy-record
Record HTTP/HTTPS traffic through the dev-proxy-recorder. Covers starting the proxy, session management, proxy.yaml routes, and HTTPS interception setup.
Best use case
proxy-record is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Record HTTP/HTTPS traffic through the dev-proxy-recorder. Covers starting the proxy, session management, proxy.yaml routes, and HTTPS interception setup.
Teams using proxy-record should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/proxy-record/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How proxy-record Compares
| Feature / Agent | proxy-record | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Record HTTP/HTTPS traffic through the dev-proxy-recorder. Covers starting the proxy, session management, proxy.yaml routes, and HTTPS interception setup.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# proxy-record skill
Use this skill when the user wants to:
- Capture HTTP or HTTPS traffic from an application
- Create named recording sessions for different test scenarios
- Configure which hosts to record via proxy.yaml
- Set up HTTPS interception with the local CA
## Starting the proxy (record mode)
```bash
dpr start
```
Default output on startup:
- Proxy: http://127.0.0.1:8080
- Web UI: http://127.0.0.1:3400
- Mode: RECORD
- Session: today's date (auto-created)
## Configuring routes (proxy.yaml)
```yaml
routes:
- match: "api.stripe.com"
upstream: https://api.stripe.com
record: true
replay: true
- match: "api.sendgrid.com"
upstream: https://api.sendgrid.com
record: true
replay: true
# Catch-all for any unmatched host
- match: "*"
upstream: "" # pass through without recording
record: false
replay: false
```
`match` is an exact hostname or hostname:port. Subdomains are matched if the host ends with `.match`.
## Named sessions
Each recording is grouped into a session. Create named sessions for different scenarios:
```bash
# Create a new session
dpr sessions new stripe-checkout-flow
# List all sessions
dpr sessions
# The session name also sets the active session context
```
Via API:
```
POST /api/sessions
{ "name": "stripe-checkout-flow" }
```
## Configuring your client
### curl
```bash
curl -x http://127.0.0.1:8080 https://api.stripe.com/v1/customers \
-H "Authorization: Bearer sk_test_..."
```
### Node.js (global proxy env vars)
```bash
HTTP_PROXY=http://127.0.0.1:8080 \
HTTPS_PROXY=http://127.0.0.1:8080 \
node your-app.js
```
### Node.js (axios)
```javascript
const axios = require('axios');
const { HttpProxyAgent } = require('http-proxy-agent');
const { HttpsProxyAgent } = require('https-proxy-agent');
const agent = new HttpsProxyAgent('http://127.0.0.1:8080');
const res = await axios.get('https://api.stripe.com/v1/customers', {
httpsAgent: agent,
});
```
## HTTPS interception
Required to record HTTPS traffic:
1. Generate and trust the local CA:
```bash
sudo security add-trusted-cert -d -r trustRoot \
-k /Library/Keychains/System.keychain \
~/.dpr/ca.crt
```
2. The CA cert path is `~/.dpr/ca.crt`. Generated automatically on first `dpr start`.
3. For Node.js, you may also need:
```bash
NODE_EXTRA_CA_CERTS=~/.dpr/ca.crt node app.js
```
## Exporting recordings
```bash
# Export as HAR file (stdout)
dpr export stripe-checkout-flow
# Save to file
dpr export stripe-checkout-flow > session.har
```
Or in web UI: Session detail -> Export HAR button.
## Environment variables
```
DPR_PROXY_PORT=8080 Proxy port
DPR_API_PORT=3400 Management API port
DPR_SESSION=my-session Active session name
DPR_WEB_ENABLED=1 1=show web UI
```Related Skills
health-records-vault
Encrypted personal health document storage system. Use when you need to upload, browse, download, or share encrypted health documents, generate share links, export a backup archive, or understand the AES-256-GCM security model. Triggers include "upload health record", "encrypt document", "share medical file", "vault backup", "download record", "health record storage", or any task involving personal medical documents.
dns-record-manager
Operate dns-record-manager -- manage DNS records across Cloudflare and Route 53, review change history, and configure providers.
ssl-proxy
Terminate HTTPS locally for development servers with auto-generated trusted certificates. Use when you need HTTPS on localhost, are testing Stripe webhooks that require HTTPS, building service workers (which require HTTPS), testing mixed-content policies, or any scenario where your local dev server must be accessible via https://. Triggers include "HTTPS locally", "trusted cert localhost", "https dev server", "SSL local", "mkcert", "browser security warning", "service worker local", "mixed content error".
proxy-replay
Replay recorded HTTP/HTTPS traffic using dev-proxy-recorder. Covers starting replay mode, selecting sessions, miss handling, and switching between record and replay.
http-proxy
Node.js HTTP/HTTPS transparent reverse proxy implementation patterns, including header forwarding, body streaming, latency measurement, and SSE for real-time events
api-analytics-proxy
Transparent HTTP reverse proxy that records every request and response to SQLite and exposes a React dashboard for traffic analytics, latency percentiles, and error inspection
health-records
Manage per-animal health event records, follow-up scheduling, and treatment cost tracking. Use when asked to add a vet visit note, record a treatment with cost, set a follow-up date, view all events for one animal, filter events by type across the herd, or export health history to CSV. Triggers include "vet visit", "treatment record", "follow-up date", "health event log", "export health history", "cost tracking", or any task focused on individual health event documentation rather than vaccination scheduling.
Skill: Uptime Monitoring
## Overview
Skill: Status Page
## Overview
Skill: unit-conversion
## Overview
Skill: recipe-scaler
## Overview
reading-list
Operate the reading-list API to save, manage, tag, search, and export articles.