Atlas / Skills / liaohch3 / Real E2e Test

Real E2e TestSAFE

skills/liaohch3/real-e2e-test

Intercept and inspect Coding Agent API traffic from Claude Code, Codex CLI, Gemini CLI, Cursor CLI, OpenCode, Kimi/Kimi Code, Pi, and Hermes in a local trace viewer.

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
—
Hosts
1 documented
License
MIT
Stars
3,277
01

Overview

Intercept and inspect Coding Agent API traffic from Claude Code, Codex CLI, Gemini CLI, Cursor CLI, OpenCode, Kimi/Kimi Code, Pi, and Hermes in a local trace viewer.

Read from source at commit 4c2d422a35f5OBSERVED · 2026-10-12
02

Install

Commands as the repository documents them. They are shown, not run.

uv run pytest tests/e2e/ --run-real-e2e --timeout=300 -v
uv run pytest tests/e2e/test_real_proxy.py::TestRealProxy::test_single_turn --run-real-e2e --timeout=180 -v -s
uv run pytest tests/e2e/ --run-real-e2e --timeout=300 -v -s --tb=long
03

Host compatibility

What the documentation claims. We have not run a compatibility test.

HostStatusNotes
claude-codementioned
04

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: real-e2e-test
description: Run real E2E tests against Claude CLI in pytest and tmux modes
tags: testing, e2e, integration, tmux
---

# Real E2E Test Skill

Run real end-to-end tests that start `claude-tap` from local source, connect to the
real Claude CLI, and verify trace output.

## Prerequisites

- `claude` CLI installed and authenticated
- Python dev dependencies installed: `uv sync --extra dev`
- `tmux` installed for interactive mode (`brew install tmux`)

## Mode 1: Pytest Real E2E (7 test cases)

### Run all real E2E tests
```bash
uv run pytest tests/e2e/ --run-real-e2e --timeout=300 -v
```

### Run a single test
```bash
uv run pytest tests/e2e/test_real_proxy.py::TestRealProxy::test_single_turn --run-real-e2e --timeout=180 -v -s
```

### Run with debug output
```bash
uv run pytest tests/e2e/ --run-real-e2e --timeout=300 -v -s --tb=long
```

## Mode 2: tmux Interactive Real E2E

Use this when you need to validate non-`-p` interactive behavior in Claude Code TUI.

```bash
scripts/run_real_e2e_tmux.sh
```

Optional overrides:

```bash
PROMPT_ONE="Use the shell tool to run command ls in the current directory, then reply with any 5 filenames only." \
PROMPT_TWO="Thank you." \
SUBMIT_KEY="Enter" \
PERMISSION_MODE="bypassPermissions" \
scripts/run_real_e2e_tmux.sh
```

Important tmux interaction notes:

- Submit key is `Enter` for Claude Code TUI in tmux (confirmed working).
- `PROMPT_ONE` should intentionally trigger tool use.
- For portability, use `grep -F` instead of `rg` in shell assertions (`rg` may be unavailable).

## Verification Checklist (for both modes)

- Latest trace `.jsonl` contains both prompts (`PROMPT_ONE`, `PROMPT_TWO`)
- At least 2 requests hit `/v1/messages`
- At least one response content block has `"type": "tool_use"`
- HTML viewer file is generated (`trace_*.html`)

## Notes

- Real E2E tests are skipped by default; `--run-real-e2e` is required.
- Each pytest case starts a fresh proxy server and trace directory.
- Timeouts are intentionally generous because real API calls are involved.
- tmux mode includes retry logic for prompt submission and post-run JSONL assertions.

## Pytest Test Cases

| Test | Timeout | What It Tests |
|------|---------|---------------|
| `test_single_turn` | 180s | Basic prompt/response trace capture |
| `test_multi_turn` | 300s | Conversation memory with `-c` flag |
| `test_tool_use` | 180s | Tool use generates multiple trace records |
| `test_html_viewer_generated` | 180s | HTML viewer generated with embedded trace data |
| `test_api_key_redaction` | 180s | API keys redacted from trace output |
| `test_streaming_sse_capture` | 180s | SSE events captured in streaming mode |
| `test_trace_summary` | 180s | CLI stdout includes trace summary and API call count |
05

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryWARN
L1Static analysis of the codeNA
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (1)

MEDIUMInventory / provenance · inv.symlink · CWE-1104
.claude/skills
.claude/skills
Why it matters. link not followed

Gates applied: no_behavioural_pass.

Audited 2026-10-12 · audit v0.4.1 · source sha 4c2d422a35f5full audit observations/trust-audit/skill/liaohch3__real-e2e-test.json · Report an issue / request a re-scan
06

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-124c2d422a35f5SAFEB89first audit
07

Questions

What does the Real E2e Test skill do?

Intercept and inspect Coding Agent API traffic from Claude Code, Codex CLI, Gemini CLI, Cursor CLI, OpenCode, Kimi/Kimi Code, Pi, and Hermes in a local trace viewer.

Is Real E2e Test safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can Real E2e Test access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

Which assistants does Real E2e Test work with?

Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.

How current is this page?

The grade is for one exact copy of the source (4c2d422a35f5), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement