claude-tap is a local proxy and trace viewer for AI coding agents, recording and displaying their API requests, prompts, tool calls, responses, context, and token usage. It helps developers inspect and compare agent runs from tools such as Claude Code, Codex CLI, Gemini CLI, Cursor CLI, and others, while the catalogue skills and instruction support work with the project.
Borrowing it
Nothing to install: this file belongs to liaohch3/claude-tap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/liaohch3/claude-tap/main/.agents/skills/e2e-test/SKILL.mdgit clone --depth 1 https://github.com/liaohch3/claude-tapWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/liaohch3/claude-tap/e2e-test)<a href="https://agentmods.dev/skills/liaohch3/claude-tap/e2e-test"><img src="https://agentmods.dev/badge/skills/liaohch3/claude-tap/e2e-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/liaohch3/claude-tap/e2e-test"><img src="https://agentmods.dev/badge/skills/liaohch3/claude-tap/e2e-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00016 | $0.00394 |
| Opus 5.5 | $0.00006 | $0.00158 |
| Sonnet 5.5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
e2e-test scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
claude-tap E2E Test
Run this skill after modifying core logic in claude-tap, especially:
- Proxy handler / SSE reassembly (
__init__.py) - TraceWriter (JSONL writing, flush behavior)
- HTML viewer generation (
viewer.html,_generate_html_viewer) - LiveViewerServer (SSE streaming)
- Signal handling / graceful shutdown
- Manual update command / trace cleanup
Steps
- Run the full test suite:
uv run pytest tests/test_e2e.py -v --timeout=120
Or run a single test:
uv run pytest tests/test_e2e.py::test_e2e -v # Full E2E pipeline
uv run pytest tests/test_e2e.py::test_trace_cleanup -v # Trace cleanup
uv run pytest tests/test_e2e.py::test_startup_does_not_contact_pypi -v # No startup update network
-
Read the output. Each test prints
PASSEDorFAILED. -
If tests fail, check:
- test_e2e fails: Core proxy pipeline issue. Check
proxy_handler,_handle_streaming,TraceWriter.write. - test_trace_cleanup fails: Manifest logic issue. Check
_load_manifest,_cleanup_traces,_register_trace. - test_startup_does_not_contact_pypi fails: Startup made an unexpected update-related network request.
- test_live_viewer_ fails*: Viewer HTML issues. Check
viewer.htmlforpreserveDetailchain,updateNavButtons. - Timeout: May be a network/port issue, not a claude-tap bug.
- test_e2e fails: Core proxy pipeline issue. Check
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 41 lines · 16 tokens per session scan A 1c74fd5f1c24
e2e-test is a skill published in the GitHub repository liaohch3/claude-tap (3,312 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 394 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
prodtest
Senior-QA test pass on a newly implemented feature. Detects the project's real test stack, writes unit and functional/integration tests, then drives the running app with Playwright for end-to-end coverage, saving screenshots to a gitignored folder for human review. Asks upfront whether found bugs should be fixed or…
behavioral-a11y
Load this skill when writing, reviewing, or interpreting behavioral accessibility automation — tests that manipulate a rendered page (resizing the viewport, pressing real keys, capturing and comparing screenshots) rather than only inspecting static markup or a single computed accessibility tree. Covers Reflow risk (SC…
axe-rules
Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.
cli-audit
Audit live URLs using Playwright and Axe combined with WCAG skills.
test-e2e
Generates end-to-end tests for a user flow using Playwright or Cypress.
qa
QA Specialist Agent for smoke testing production deployments. Runs Playwright-based smoke tests against live URLs to verify health, auth flows, protected routes, and core UI. Use when validating a deploy, checking if a production app is working, or when asked to run QA on a project.