Run any Skill in Manus with one click

replay

Stars4

Forks0

UpdatedJune 10, 2026 at 17:42

Drive a reproducible HTTP replay load against a running clawback proxy. Replays one captured /v1/messages fixture at a load profile's inter-turn gap schedule, with built-in carry-over control (fresh path-mode session id + per-block cache nonce). Auth is an OAuth bearer (CLAWBACK_OAUTH_TOKEN), never an Anthropic API key; pre-flights the proxy and bearer before spending tokens. Use to generate clean, per-knob, deterministic-timing traffic for the analyzer; pair with .skills/drive (the faithful PTY arm) to cross-check.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

zapgun-ai

zapgun-ai/clawback

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name

replay

description

clawback HTTP replay load driver

Run .skills/replay/scripts/replay_load.sh from the project root. It pre-flights (proxy reachable? CLAWBACK_OAUTH_TOKEN bearer set?) and then forwards every argument to benchmark/bin/replay.js. Data is captured by the proxy's --turn-log, not by this driver — start the proxy (with its own turn-log) via .skills/monitor first.

Auth: OAuth bearer, never an API key

There is no Anthropic API key here. A real run forwards Authorization: Bearer $CLAWBACK_OAUTH_TOKEN — the same OAuth credential claude sends (Claude Max) — which clawback then forwards upstream. If you'd rather not handle the bearer directly, drive real traffic through the PTY arm (.skills/drive), which uses your actual claude login.

Spends real tokens

A non---dry-run run sends real /v1/messages requests against your Anthropic limits — the very thing clawback stretches. Budget it (cap --turns, use the cheap Haiku fixture for plumbing). --dry-run needs no bearer and no proxy.

Usage

# inspect the fixture + planned gap schedule, no proxy/bearer, no spend:
.skills/replay/scripts/replay_load.sh --dry-run --profile L0 --turns 5

# real block (proxy must be up with a --turn-log; bearer forwarded as
# Authorization, never an API key):
CLAWBACK_OAUTH_TOKEN=… .skills/replay/scripts/replay_load.sh \
  --profile L2 --turns 200 --fixture benchmark/fixtures/ccode.json \
  --port 8787 --session-id A5-L2

Key options (forwarded to replay.js; see its header for the full list)

--profile L0|L1|L2|L3|L4 — inter-turn gap range (mirrors .skills/drive).
--turns N, --gap-sec N (fixed-gap override for fast mechanics tests).
--fixture PATH — the /v1/messages body to replay.
--session-id ID — path-mode SESSION KEY; use a fresh one per block. Omitted → auto-minted per run.
--shared-cache — skip the per-block cache nonce (measure a warm start across runs). Default is FRESH: a unique nonce is prepended to system so Anthropic's prefix cache starts cold for the block (carry-over control).
--anthropic-beta STR — defaults to a realistic value including extended-cache-ttl-2025-04-11; required for arm A2 (1h-TTL) to be faithful, because clawback forwards but does not add this beta.
--stream, --model ID, --transcript PATH.

Fixture fidelity (read before quoting absolute numbers)

The shipped benchmark/fixtures/ccode.json is a sanitized real capture (one Claude Code turn captured 2026-06-02 via .skills/capture; identifiers and personal context scrubbed, cache_control breakpoints and cch structure untouched). It is faithful in shape, but Claude Code's prompt evolves with every release — for headline numbers on today's build, mint a fresh body with .skills/capture (it drives one real claude turn through a --capture-body proxy and promotes the pristine dump to a fixture), then pass it here with --fixture. Or lean on .skills/drive (the faithful real-claude arm).

After a run

When both arms' turn-logs are collected, analyze with .skills/bench:

node benchmark/bin/analyze.js --out runs/report-$(date +%s) \
  --label A0=runs/A0.ndjson --label A5=runs/A5.ndjson

More from this repository

same repository

zapgun-ai/clawback

Run a counterbalanced A/B knob block end to end and produce a report. Orchestrates the whole validation loop the other skills do piecemeal — for each arm it starts a clawback proxy with that arm's knobs and its OWN --state file (fresh SESSION KEY, no clawback-side carry-over), drives N turns of load through it (pty or replay driver), stops it, then analyzes the per-arm turn-logs and renders the charts. No cache-salt: production forwards none, so neither does the harness. Default block is A0 (passthrough baseline) vs A5 (recommended stack); the analyzer pools all passthrough turns into the baseline and compares each treatment arm against it, so the block must include A0 and may carry several treatment arms at once. Use this to run the full A/B runbook in one command. The pty driver spends real Anthropic tokens (one run per arm) — pin --model.

2026-06-104

armstat

zapgun-ai/clawback

Fast, read-only per-arm turn-log summary — billable turn count, httpStatus tally (catches rate-limiting / non-200s mid-run), cache_read/creation sums with the ephemeral 5m-vs-1h split (a direct knob-sanity check: A2/A3/A5 should show ephemeral_1h > 0, A0/A1/A4 should not), token-weighted hit rate, and thinkingBudget. Unlike the heavyweight `bench` analyzer it does no bootstrap/CI/pricing, so it is cheap to run at each arm boundary WHILE a suite is still in flight. Safe on a live, actively-appended NDJSON file (a partial trailing line is skipped). Use it to spot-check a just-finished arm before the next one starts.

2026-06-104

bench

zapgun-ai/clawback

Analyze clawback turn-logs (NDJSON) to compare treatment vs passthrough arms. Produces report.md, report.csv, summary.json, manifest.json. Headline is billable input tokens reclaimed per turn (full-rate quota saved, no pricing) with a bootstrap 95% CI; per-turn $ and hit-rate are a demoted cost appendix, all stratified by inter-turn gap bucket. Use after the operator has collected counter-balanced windows.

2026-06-104

capture

zapgun-ai/clawback

Capture a REAL Claude Code /v1/messages body as a replay fixture, so the HTTP replay arm (.skills/replay) faithfully reproduces Claude Code's cache_control breakpoint structure (a hand-authored fixture makes the 1h-TTL knob look like a no-op). Starts a clawback proxy with --capture-body, drives ONE real claude turn through it via the PTY driver, verifies the dump carries cache_control breakpoints, and promotes it to the fixture path. Spends real Anthropic tokens (exactly one turn; pin a cheap model with --model). Use once before replay-based benchmarking, or to refresh the fixture when Claude Code changes its request shape.

2026-06-104

card-tones

zapgun-ai/clawback

Render the clawback share card in BOTH tones (neg + pos) as a DESIGN render-only proof — NOT a benchmark result — so the share-card atmosphere (deep-purple LENS_CORE centre, win-only cyan corona, darkened gradients) can be eyeballed in one pass. neg uses a real run's amber regression card (purple core, no corona); pos is a SYNTHETIC fixture built only to exercise the renderer's win branch (purple core + cyan corona) — its number is fabricated, never published. Delegates to the shared preview_card.sh. Use when tweaking the share-card renderer's visuals and you want to see both tones side by side.

2026-06-104

drive

zapgun-ai/clawback

Drive the REAL claude binary through clawback's PTY channel at a scripted inter-turn gap schedule — the faithful load arm. Because the bytes on the wire are produced by genuine Claude Code, this is the only driver that exercises the 1h-TTL nested-cache-control rewrite (arm A2) authentically. Use for headline/moat numbers and to cross-check the HTTP replay arm (.skills/replay). Requires node-pty and a running clawback proxy.

2026-06-104

name

replay

description

clawback HTTP replay load driver

Auth: OAuth bearer, never an API key

Spends real tokens

Usage

# inspect the fixture + planned gap schedule, no proxy/bearer, no spend:
.skills/replay/scripts/replay_load.sh --dry-run --profile L0 --turns 5

# real block (proxy must be up with a --turn-log; bearer forwarded as
# Authorization, never an API key):
CLAWBACK_OAUTH_TOKEN=… .skills/replay/scripts/replay_load.sh \
  --profile L2 --turns 200 --fixture benchmark/fixtures/ccode.json \
  --port 8787 --session-id A5-L2

Key options (forwarded to replay.js; see its header for the full list)

--profile L0|L1|L2|L3|L4 — inter-turn gap range (mirrors .skills/drive).
--turns N, --gap-sec N (fixed-gap override for fast mechanics tests).
--fixture PATH — the /v1/messages body to replay.
--session-id ID — path-mode SESSION KEY; use a fresh one per block. Omitted → auto-minted per run.
--shared-cache — skip the per-block cache nonce (measure a warm start across runs). Default is FRESH: a unique nonce is prepended to system so Anthropic's prefix cache starts cold for the block (carry-over control).
--anthropic-beta STR — defaults to a realistic value including extended-cache-ttl-2025-04-11; required for arm A2 (1h-TTL) to be faithful, because clawback forwards but does not add this beta.
--stream, --model ID, --transcript PATH.

Fixture fidelity (read before quoting absolute numbers)

After a run

When both arms' turn-logs are collected, analyze with .skills/bench:

node benchmark/bin/analyze.js --out runs/report-$(date +%s) \
  --label A0=runs/A0.ndjson --label A5=runs/A5.ndjson