06-reference

alphasignal claude job agent pxpipe api cost

2026-07-06·reference·source: AlphaSignal·by AlphaSignal

AlphaSignal — Claude job-search agent + pxpipe 70% API cost cut (Jul 6 2026)

Why this is in the vault

Two items in this issue land directly on RDCO's active surface: a Claude-powered job-search agent that demonstrates a dual-agent review pattern in the wild, and pxpipe — a local proxy that cuts Claude Code API costs 59–70% by exploiting the gap between image and text token pricing. Both are immediately applicable to RDCO's always-on agent infrastructure.

⚠️ Sponsorship

Three paid placements in this issue:

All curated items are delivered through AlphaSignal click-tracking redirects (app.alphasignal.ai/c?...). The three editorial top-repo picks are non-sponsor selections.

Issue contents

1. reMarkable tablet → Harry Potter AI diary (Riddle)

15k likes. Rust-based project by an independent developer. User writes with a stylus; after a 2.8-second pause the handwriting is sent as an image to a vision model, which replies in flowing handwritten strokes. Supports any OpenAI-compatible API. First response appears in ~1 second, streaming sentence-by-sentence. MIT license, requires SSH access on a reMarkable Paper Pro. Relevant as a creative human-in-the-loop physical input pattern.

2. ai-job-search — Claude agent auto-applies for jobs (4.4k GitHub stars)

Built by Mads Lorentzen (PhD geophysicist who automated his own job hunt). Flow: user fills in background profile once → agent reads a job posting → scores fit → drafts tailored CV (pulls only relevant experience) → writes a cover letter framed for the specific role → a second agent reviews the first agent's output, flags weaknesses → first agent revises → compiles both into clean PDFs.

Requires Anthropic API key or Claude Pro + Python 3.10+. MIT license. gh repo fork MadsLorentzen/ai-job-search --clone to try.

Pattern note: the first-draft → critic → revision cycle is a clean open-source reference implementation of what RDCO's fresh-eyes subagent SOPs formalize.

3. pxpipe — 59–70% Claude Code cost reduction via image proxy

Local TypeScript proxy (MIT, ~586 GitHub stars). Takes the bulk of every Claude Code request — system prompt, tool docs, chat history — and converts it to dense PNG images before sending. Exploits a pricing asymmetry: image token cost is pixel-based, not content-density-based, so 25k text tokens compress to ~2.7k image tokens. Reported savings in production: one session dropped from $42.21 to $6.06 on Fable 5.

Setup: npx pxpipe-proxy → set ANTHROPIC_BASE_URL=http://127.0.0.1:47821 → run claude. Live dashboard shows per-request savings.

Critical caveat — lossy OCR: exact strings (hex IDs, secrets, file hashes) can be silently misread. Fable 5 reads dense hex correctly ~13/15 times; Opus gets 0/15. pxpipe auto-routes byte-sensitive values as plain text, but the gap is real and the failure mode is silent confabulation.

4. OpenMed — on-device clinical PII redaction (755 tok/s on Mac)

1,494 likes. On-device model running at 755 tokens/second on Apple Silicon. Relevant for any agentic pipeline that handles personally identifiable content without wanting cloud round-trips. Filed for future reference on RDCO data-privacy use cases.

5. Open-source format for reusable AI agent skills

22k GitHub stars. Packages reusable skills directly into agent definitions as a portable format. Architecture echoes RDCO's ~/.claude/skills/ pattern — worth pulling the spec when the repo surfaces.

6. Sakana Fugu — multi-agent orchestration system (ICLR 2026)

Based on two ICLR 2026 papers (TRINITY + Conductor). Treats a pool of specialist agents as an orchestrated ensemble rather than a single scaled model. In a Sudoku variant benchmark, the multi-agent coordination approach hit ~93% vs 11% baseline. Core thesis: learning to route tasks to specialist agents outperforms scaling a single monolithic model.

7. Signals (brief)

Mapping against Ray Data Co

pxpipe's 70% cost cut is immediately testable on RDCO's Mac Mini Claude session — but the lossy OCR failure mode is the exact anti-pattern CLAUDE.md's "no batched result declaration" rule exists to catch. The Mac Mini always-on agent reads file paths, git SHAs, tool call IDs, and exact flag strings throughout its normal operating cycle. A silently misread SHA or path would produce a declared-but-wrong outcome invisible to the session. Practical decision: if pxpipe is evaluated, scope it to narrative-only context slices (long planning prompts, explanation blocks) and explicitly exclude any context that contains IDs, hashes, or exact string matches. Do not apply globally to the harness until a regression test confirms no tool-call degradation.

The ai-job-search dual-agent review pattern (drafter → independent critic → revision) is a production implementation of what RDCO's /verify-strategic-output, /verify-vault-write, and /verify-dispatch SOPs are building. Lorentzen's open-source version can be read as a minimal reference architecture: two agents, one task handoff, one revision cycle, clean PDF output. The gap vs RDCO's pattern is the automated feedback write-back — RDCO's verification currently stops at a report, not a revision loop.

Sakana Fugu's ICLR-backed thesis that specialist agent pools outperform monolithic scaling validates both RDCO's hub-and-spoke multi-agent approach and the phData DSA positioning — many specialist agents per engagement outperforms one generalist.

Related