06-reference

alphasignal claude code free proxy glm legal

2026-10-13·reference·source: AlphaSignal·by Lior Alexander
alphasignalclaude-codeopen-weight-modelssecuritylegal-ai

Why this is in the vault

Captures a free-proxy GitHub tool that silently reroutes Claude Code's own API traffic through 53 third-party providers, plus a concrete new data point (Z.ai's GLM-Legal) for the open-weight-beats-frontier-at-a-fraction-of-cost pattern already under watch.

Mapping against Ray Data Co

The single most concrete connection: the lead Top Repo item (55,000+ GitHub stars, 6,399 likes) is a tool that makes Claude Code "think it's talking to Anthropic" while actually pooling every request across 53 free providers (DeepSeek, Kimi, Groq, Gemini) for 1.3 billion free tokens/month, auto-failing over between them. This is exactly the install class feedback_mcp_install_security_review_default exists for — a MITM-style proxy that intercepts a paid agent harness's own authenticated traffic and silently reroutes it through dozens of unvetted third parties is a materially different risk profile than a typical MCP server install, not a free subscription hack to try casually. The founder runs Claude Code as the primary agent harness end to end (reference_claude_plan_max20x.md — Max 20x at $200/mo, API-credit-backed) — this entire conversation is running inside Claude Code — so "swap in the free proxy" is precisely the tempting, unreviewed substitution this memory is designed to catch before it happens, not after.

Second, lower-signal: Z.ai's GLM-Legal (19.2% all-pass rate on the Harvey LAB legal benchmark, tripling its GLM-5.3-Flash base model's 6.7%, at $0.15/task vs. $10.55 for Gemini 4 Argon) is another concrete instance of the "specialized, efficient, open beats frontier-closed" thesis the issue's own intro states outright. This reinforces the pattern already tracked against TypeSafe's Jev vs. the open CLM-8B model in [[2026-09-27-alphasignal-system-one-models-jev-laya-clm8b]] — a second and third domain (legal, not just judge-pattern benchmarks) now showing the same cost/capability inversion, worth folding into any future model-vendor choice under project_phdata_cert_escalator_path or project_credibility_for_phdata_sales.

Curation section

⚠️ Sponsorship

Three distinct paid placements this issue, all already-confirmed rotating-pool members (per 01-projects/process-newsletter/README.md, pool stood at 35+ distinct sponsors as of 2026-10-09) — no new sponsor to log:

Masthead "In Partnership with" slot is present but unresolved in plaintext — renders as "In Partnership with · Today's Author" with no legible partner name in between, consistent with the majority-unresolved pattern logged since 2026-09-14.

Related