|
Two days after the Fable 5.1 launch hype, the measurements started arriving — and they cost about three times as much as the demos suggested. Meanwhile the subs spent the day roasting their own tooling, and one user posted a prompt injection their setup caught before it did anything
Today in 30 seconds
1. Fable 5.1’s bill arrives
2. Access and limits, not capability
3. The subs are roasting their own output
4. A prompt injection caught in the wild
1Fable 5.1’s bill arrives
The launch demos and the benchmark run landed on the same day and told different stories. A repeat MineBench run put Fable 5.1 at $147.55 for 15 builds against Fable 5’s $54.93 — roughly 3x the cost at the same advertised API price, with about 2x the inference time and output size barely moving. On the demo side, a user reported building a working Minecraft mod (Blender models, textures, video analysis, in-game testing) for about $20.
→ Why it matters: Same posted per-token price, roughly triple the actual spend — the difference is reasoning time, which no pricing page shows. If you budget agent work by list price, re-measure against your own workload before committing to 5.1.
Differences Between Fable 5 and Fable 5.1 on MineBenchr/ClaudeAI
540 up / 36 comments. One person’s benchmark, not a controlled study — but it reports method and totals: $147.55 vs $54.93 across 15 builds, 40m vs 18m average inference.
Fable 5.1 made a Minecraft mod for $20r/ClaudeAI
1.9k up / 206 comments. Anecdotal build report — two YouTube links in, a Fabric 1.21.1 mod with Blender-made models out. The most-asked question in the replies was how much manual fixing came after the first run.
2Access and limits, not capability
Most of the friction posted wasn’t about what the models can do. Pro subscribers pushed for Fable to come back to the $20 tier after its removal, with the recurring ask being a hard percentage cap rather than a total block. Separately, a new `/limit-reset` command surfaced in Claude Code that clears a session limit once per week — reportedly drawing against the weekly allowance to do it. And Meta shipped Muse Spark 1.3 at $0.10/$0.20 per million tokens.
→ Why it matters: Plan design is now the thing people actually feel day to day. If you’re standing up agent work for a team, price the tier and the reset rules alongside the model — a capped-but-available expensive model beats an unavailable one for most real workflows.
Anthropic, we want Fable back into the pro planr/ClaudeAI
502 up / 197 comments, and contested — plenty of replies argue one Fable prompt would eat a Pro user’s whole quota anyway. Commenters note the removal predates the 5.1 release.
`/limit-reset` resets your session limit once per weekr/ClaudeCode
431 up / 66 comments. Appeared unannounced on hitting a session limit; the poster says it worked. Others report it showing but not being usable, and question the weekly-usage trade-off.
Meta releases Muse Spark 1.3 at $0.10 in / $0.20 out per million tokensr/ClaudeAI
446 up / 103 comments. Benchmark claims only so far — the top reply is straightforward wait-and-see, and nobody in the thread reported real coding use yet.
First model to out-lead Claude on Code Arena in a long timer/ClaudeAI
273 up / 65 comments, and the thread is mostly benchmark skepticism rather than celebration — several ask for a benchmark of benchmarks first.
3The subs are roasting their own output
A large share of the day’s top posts were jokes at the tooling’s expense. The best-performing one was a rant screenshot of an over-commented AI pull request, where the sharpest reply described the comments as a lossy copy of the prompt written back into the repo. A satirical ‘I built a full game in under an hour’ post drew 168 comments, and the author had to add a note clarifying it was a joke
→ Why it matters: Comment bloat is a real cost, not just a style complaint — one commenter reported cutting about 24,000 generated comments by 80% after an audit. Worth a lint rule or a standing instruction rather than a cleanup pass later.
My average Opus 5 experiencer/ClaudeCode
1.2k up / 154 comments. A screenshot of a comment-saturated diff. The replies read like a shared code-review checklist for generated PRs.
Fable 5.1 Max gave me the most reasonable local setup guider/ClaudeAI
2.8k up / 86 comments — the day’s top post, and a joke. Top replies split between the absurd hardware ask and a jab at training-data provenance.
What Claude sees when inspecting my codebaser/ClaudeCode
457 up / 47 comments. A visual pun on ‘load-bearing.’ The replies are a greatest-hits reel of the model’s stock phrases.
4A prompt injection caught in the wild
A user posted an injection attempt that their agent flagged rather than followed — text trying to get a Vercel token exfiltrated, most likely arriving through an npm dependency. They swept the system afterward and found nothing left behind. The thread’s useful turn was a commenter asking whether agent security is becoming more a property of the surrounding tooling than of the model
→ Why it matters: The injection came in through the dependency tree, not the user. Treat package installs in an agent’s working directory as untrusted input, and keep tokens out of the environment the agent can read.
Well I almost got prompt injectedr/ClaudeAI
703 up / 57 comments. The poster was running Claude Code against a self-hosted litellm + llama.cpp backend; the source was never fully confirmed beyond ‘likely npm.’
From the comments
“At this point the comments are just a lossy serialization of the prompt into the repo, so the next agent gets to pay context tax for reading its own autobiography.”
159 upvotes on the over-commented-PR thread in r/ClaudeCode — the clearest statement of why comment bloat compounds.
“Output size barely moved, 30.65 to 34 MiB average, while the cost tripled.”
26 upvotes on the MineBench comparison in r/ClaudeAI, isolating reasoning time as the source of the 3x.
“I really wonder if agent security is becoming more about the harness than the model itself.”
43 upvotes on the prompt-injection post in r/ClaudeAI.
🧵 Beyond the Thread
Releases and what the community is reading — with a quick read on each.
Releases
v2.1.259★ Notable
Solid maintenance release; the concurrent session data-loss fix alone makes upgrading worth it for multi-session users.
• Concurrent sessions no longer silently clobber ~/.claude.json — workspace trust and MCP state preserved
• managedMcpServers org setting: push HTTP/SSE MCP servers to all users centrally
• –permission-prompts none for headless/unattended runs: blocked prompts auto-denied
• Bash Read() deny rules now cover option-value paths, compound commands, recursive grep/cp
Hacker News
Check if a file was made with Claude
C2PA metadata strip with Ctrl+Shift+V — not a real detection tool, more provenance theater.
• Anthropic’s check-content page uses C2PA file metadata, not text watermarking
• C2PA is trivially stripped; HN commenters note paste-as-plain-text defeats it instantly
• Distinct from SynthID-style hidden watermarks — much weaker guarantee
• No enforcement mechanism; answers ‘did Claude touch this file,’ not ‘is this AI content’
172 points · 128 comments · HN
Six curl CVEs after OpenAI and Anthropic came back with zero
Real result but zero technical detail on method; 29 reports → 6 CVEs ratio matters more than the headline.
• AISLE found 6 confirmed curl CVEs after Anthropic Mythos and OpenAI Codex Security reported zero
• 29 raw reports submitted; 6 confirmed — signal-to-noise ratio not discussed in post
• No technical explanation of tooling or approach, just competitor comparison
• HN commenters note good marketing but flag missing methodology as the real gap
171 points · 56 comments · HN
Show HN: Kit. Claude Code but Concise
Early-stage personal project claiming context efficiency gains; minimal community validation yet.
• Headless agent TUI built to minimize context window usage
• Supports dynamic skill/plugin reload at runtime
• One dev replaced Claude Code and Codex with it daily
• 12 HN points, 1 comment — no real community signal yet
12 points · 1 comments · HN |
