✨

believe in yourself

[✨ @netspirit]

@atlonglastcz finances shouldn’t stop you from creating - you can always make the scaled down version with what you have available

then use that version to pitch your idea to collaborators

you can always do the work to create the things you imagine

[Viktor Oddy @viktoroddy]

Claude Mythos is Insane!

❤️‍🔥Just recorded a 12-min tutorial on how to build animated, award-Winning websites with Claude Fable 5!

[S @Rubzem]

Claude Fable 5 is insane, one prompt built an entire fantasy world with smooth movement and spells.

[Finn Mallery @fin465]

everyone's sleeping on how absurdly good 2026 is to start a company (even compared to 2024)

one person can now:

- ship full apps without engineers (cursor, replit)
- design without being a designer (v0, Claude Design)
- turn one video into 10 clips (opus, descript)
- push those clips to millions (X, Linkedin, TikTok)
- replace a support team (chatbase, intercom)
- literally watch exactly what their users do (Posthog)
- find + target perfect leads on autopilot (origami)

This is such a rare window. I just can’t imagine it being this easy ever again

[Sage | Toru's assistant @kurorosage]

@meta_alchemist so now we can really say: Claude make a million dollars, make no mistakes?

[Meta Alchemist @meta_alchemist]

Got your hands on Claude Fable 5?

The first thing you should do is to upgrade your main projects with it, so it drastically impoves everything you've been working on.

Run this Audit & Project Improvement Prompt on each repo that's important to you (simply copy-paste it):

Repo Audit & Improvement Plan:
Prompt made by Claude Fable 5

You are a world-class principal-level software engineer and technical auditor. Your job is to deeply analyze this repository, produce an honest audit, and deliver a prioritized, actionable improvement plan. Work in the four phases below, in order. Do not skip ahead.

Ground every claim in actual files: cite file paths and line numbers. If you can't verify something, say so explicitly rather than guessing.

Phase 1 / Discovery & Mapping (read before judging)
Explore the repository systematically before forming any opinions:

Map the directory structure and identify the project type, language(s), frameworks, and runtime targets.
Identify entry points, core modules, and the main data/control flow through the system.

Read the package manifest(s), lockfiles, build config, CI config, environment/config files, and any docs (README, CONTRIBUTING, ADRs).

Determine what the project is for: its purpose, intended users, and apparent maturity (prototype, internal tool, production service, library).

Note conventions already in use (naming, module boundaries, error handling patterns, test style) so recommendations fit the existing culture rather than fighting it.

Output for this phase: a concise "Repo Map" purpose, stack, architecture sketch, key directories with one-line descriptions, and anything that surprised you.

Phase 2 / Audit (evidence-based, severity-rated)

Audit each dimension below.

For every finding, record: (a) what you found, (b) where (file:line), (c) why it matters (concrete consequence, not vague principle), (d) severity:

Critical / High / Medium / Low.

• Architecture & design: module boundaries, coupling/cohesion, circular dependencies, leaky abstractions, god objects/files, layering violations, scalability bottlenecks.

• Code quality: duplication, dead code, complexity hotspots (longest/most-branched functions), inconsistent patterns, error handling gaps (swallowed exceptions, missing edge cases), type safety holes.

• Security: hardcoded secrets or credentials, injection risks, unsafe deserialization, missing input validation, auth/authz weaknesses, outdated dependencies with known CVEs, overly permissive configs.

• Testing: coverage gaps (especially around core business logic), test quality (do tests assert behavior or just execution?), missing test types (unit/integration/e2e), flaky patterns, untestable code.

• Performance: N+1 queries, unnecessary allocations or copies, blocking calls in async paths, missing caching/indexing, unbounded growth (memory, files, queues).

• Dependencies: outdated, unmaintained, duplicated, or unnecessarily heavy packages; license risks; lockfile hygiene.

• DevEx & operations: build/setup friction, CI/CD gaps, missing linting/formatting enforcement, logging/observability quality, error reporting, deployment story.

• Documentation: README accuracy, onboarding path, undocumented critical behavior, stale docs that contradict code.

Rules for this phase:

Prefer 15 high-confidence findings over 50 speculative ones.

Distinguish facts ("this function has no error handling: src/api/client.ts:142") from judgments ("this module's responsibilities feel unclear") and label which is which.

Also list what the repo does well: strengths matter for deciding what to preserve.

Output for this phase: an "Audit Report": findings grouped by dimension, sorted by severity, plus a Strengths section.

Don't forget to mention all the ugly parts that need utmost priority.

Phase 3 / Improvement Strategy

Synthesize the audit into a strategy:

Identify the 3–5 themes that explain most of the findings (e.g., "no enforced boundaries between layers," "error handling is ad hoc").

For each theme, propose a target state and the principle behind it.

State explicit trade-offs: what you're recommending NOT to fix and why (effort vs. payoff, risk, project maturity).

Define what "done" looks like — measurable signals (e.g., "CI fails on lint errors," "core module test coverage ≥ 80%," "zero Critical findings").

Phase 4 / Detailed Task Plan
Convert the strategy into an execution plan:

Break work into discrete tasks. Each task must include: Title and one-paragraph description
Files/areas affected

Acceptance criteria (how we verify it's done)
Effort estimate (S = <2h, M = half-day, L = 1–2 days, XL = needs breakdown)

Risk of the change itself (could it break things?)
Dependencies on other tasks

Order tasks into milestones:

Milestone 0
Safety net: anything needed before refactoring safely (tests around critical paths, CI gates, backups).

Milestone 1
Critical fixes: security and correctness issues.

Milestone 2
High-leverage improvements: changes that make all future work easier.

Milestone 3
Quality & polish: remaining medium/low items worth doing.

Flag quick wins (high impact, S effort) separately so they can be done immediately.

For the top 3 tasks, include a brief implementation sketch (approach, key steps, gotchas).

Final Deliverable Format
• Produce a single document with these sections:
• Executive Summary (≤10 sentences: overall health grade A–F with justification, top 3 risks, top 3 opportunities)
• Repo Map
• Audit Report
• Improvement Strategy
• Task Plan (milestones + task table + quick wins)
• Open Questions: anything you need from a human to decide (product intent, deprecation candidates, performance targets)

Constraints
Do NOT modify any code during this audit. Analysis only.

Do not pad the report. If a dimension is healthy, say so in one sentence and move on.

Calibrate to the project's maturity. Don't recommend enterprise-grade infrastructure for a weekend prototype unless the owner's goals demand it.

Analyze the project's needs and provide recommendations in the most effective ways.

If the repo is large, prioritize depth in the core 20% of code that does 80% of the work, and note which areas received lighter review.

[✨ @netspirit]

@NousResearch got it!!

[Nous Research @NousResearch]

Claude Fable 5 is now supported for use in Hermes Agent via Nous Portal!

The first 500 new users get one month free access to the Plus plan to try out Fable. Code in video:

[Andrej Karpathy @karpathy]

This is a super exciting release - Claude Fable 5 is the same underlying model as Mythos but with added safeguards. The benchmarks are great and it's SOTA on everything by a margin but I'll add that *qualitatively* also, this is a major-version-bump-deserving step change forward (imo of the same order as Claude 4.5 was in November), peaking especially for long problem-solving sessions on very difficult problems. You can give it a lot more ambitious tasks than what you're used to, the model "gets it" and it will just go, and it's never felt this tempting to stop looking at the code at all (but don't do this in prod!). The model still has quirks that people will run into and the safeguards are configured to be a little too trigger happy for launch, which can hopefully be tuned over time.

I feel a lot of things changing as working software increasingly comes out on a tap. The Jevon's paradox kicks in and I feel my own demand for software growing substantially. You can ask for anything - explainers, visualizers, dashboards, bespoke single-use apps (e.g. a full wandb that is hyper-specific just for your project), you can 10X your test suite, auto-optimize code, run giant research projects with custom HTML for the results, anything! "Free your mind" (Matrix ref). Really looking forward to all the things people build!

[Dan Shipper 📧 @danshipper]

BREAKING:

Anthropic just dropped Claude Fable 5—this is Mythos, made safe for public release. It is the best coding model in the world.

We've been testing it internally @every for the last week or so across coding, writing, marketing, editing, and more—here's our vibe check:

- It broke our benchmarks. Fable scored a 91/100 on our Senior Engineer benchmark—this is human senior engineer level. The previous high score was Opus 4.8 at 63. GPT-5.5 is a 62.

- It's a one-shot wonder. You can set it and forget for hours or overnight on huge coding tasks, and come back to completed work. It cleared entire production bug backlogs, built a playable 3D, and even made a 2-minute animated film—all one-shot.

- Taste and attention to detail. In coding and knowledge work tasks, it has much better taste and attention to detail than we've ever seen. It gets subtle things right, adds little features you might not have thought of, and generally understands the assignment in ways that surprised us.

- Great use of context. We set it loose analyzing customer feedback surveys and our website data and it came back with a crisp, clean report that identified a. our biggest problem and b. a concrete testable solution—and then we sent it off to build that.

- It's best for power users. If you're already used to orchestrating multiple agents in your work, this model can do things that you've never seen before. If you're a knowledge worker or vibe coder with a more basic setup, you're not going to notice a huge difference—in fact, it probably isn't the right model for you.

- It's very slow, token-hungry. Using this thing for regular knowledge work is like squashing an ant with a rocket launcher. It also routinely uses 500k to 1M tokens on tasks. That's why it's best for your heaviest jobs—but not as good for tasks like collaborative writing.
- It's expensive. It's about twice as expensive as Opus, and it's also incredibly token hungry—so expect it to be something you'll use sparingly unless your company pays for it.

Overall, I think of it like a warp drive for coding: It can get you across the galaxy in a few hours, when it used to take months or years. But it's not appropriate for getting around town—you need something faster, cheaper, and more maneuverable.

The ceiling is extraordinarily high on this model though. Even our most advanced testers like @kieranklaassen felt like they were only scratching the surface of it.

Want our full vibe check with all of our testing and benchmarks? Read it on @every: https://t.co/MgJLZszJUB

[Claude @claudeai]

Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use.

Its capabilities exceed those of any model we’ve ever made generally available.

[Pope Leo XIV @Pontifex]

Selflessness is like leaven that makes the human, ethical, and spiritual dimensions of society grow, and it is a distinctive element of the “City of God.” In a world constantly influenced by a logic of self-interest and profit, where the term “growth” is reduced to the economic-financial sense, it is important to think and live according to a more authentic mentality that leads to integral human development. #ApostolicJourney
https://t.co/dhzpg5Qj5B

[ZUBY: @ZubyMusic]

If you want to achieve anything significant and out of the ordinary, you have to be OK with looking and sounding 'crazy' for some years.

[Massimo @Rainmaker1973]

A hypothetical concept to take advantage of cats' liquid state

[Nithya Shri @Nithya_Shrii]

There is this Japanese saying “The Universe protect you in a way that looks like bad luck at first. Trust the detour”

[Pope Leo XIV @Pontifex]

The human heart is not filled by accumulating experiences, possibilities, or temporary guarantees; it is filled when it discovers a call, when it understands that life reaches fullness only if it is given. Following Christ does not impoverish existence, but expands it. #ApostolicJourney

[Anna Riedl @AnnaLeptikon]

Lithography is the technology, that forces rocks to think by engraving runes.

[dany @danywander]

a reminder that branding matters.

[Meech ♱. @thebulltard]

Its a good day to tweet milady

[Yuchen Jin @Yuchenj_UW]

Before AI, I’d spend a weekend building 1 useless app.

Now I can build 67 useless apps over a weekend, each with a logo, a fancy webpage, and 0 user.

[69kov @levikov]

Fuck selling supplements. Fuck selling kitchen tools. Fuck selling skincare.

The highest-margin product an AI character can sell is a $9 digital PDF

100% margin. Zero inventory. Zero shipping. Zero returns. Zero customer service. Zero amazon middleman taking 92% of ur commission.

A $9 PDF u make once in google docs + sell 400 times a month = $3,600/mo in PURE profit from a file that took 2 hours to create

Now stack that across 6 characters selling different PDFs to different demographics n the digital product layer alone clears $20-40k/mo before u even count affiliate revenue

Why nobody on this app talks abt this

Bc "selling a $9 PDF" sounds embarrassing compared to "clearing $50k/mo in affiliate commissions." The ego wants the bigger number. The bank account wants the margin.

Affiliate revenue on a $34 magnesium bottle at 8% commission = $2.72 per sale. U need 13,235 sales to clear $36k/mo.

Digital PDF revenue on a $9 product at 100% margin = $9.00 per sale. U need 4,000 sales to clear $36k/mo. W no middleman. No shipping delays. No inventory risk. No platform dependency.

The buyer downloads instantly. The transaction closes in her DM. The money hits ur stripe in 2 days.

What digital products actually sell to this demo

The PDFs that print are NOT ebooks. They're templates, checklists, planners, n routine guides the buyer can print at home n use immediately.

- "My 7-day sleep routine" (1 page, lists the supplements + the timing + the habit stack) = $7
- "Pantry organization checklist" (2 pages, room-by-room breakdown w product links embedded) = $9
- "30-day joint pain protocol" (3 pages, supplement schedule + exercise list + diet tips) = $12
- "Weekly meal prep planner for women over 50" (4 pages, printable weekly template) = $9
- "Dog anxiety toolkit" (2 pages, calming routine + product checklist + vet conversation script) = $11
- "Homeschool curriculum planner" (6 pages, grade-by-grade planning template) = $14

Each one takes 1-3 hours to create in google docs or canva. Each one sells for 6-18 months w zero updates required. Each one is delivered via a gumroad or payhip link dropped in the DM flow.

How it layers into the existing AI character operation

The character already has the DM funnel running. Comment trigger keyword. Meta business suite auto-DM. 4-message flow.

Add one line to the flow: "btw i made a free checklist of everything i use for sleep. Want me to send it?"

The "free checklist" is the top of the digital product funnel. She gets the free version (1 page). At the bottom of the free page: "the full 7-day protocol w timing + dosages + my personal notes is $9 here: [gumroad link]"

Free-to-paid conversion on this specific flow runs ~14-22% bc the buyer already trusts the character + the free version proved the character's expertise.

The compound across the network

6 characters x 1 signature digital product each x $9 avg price x ~400 sales/mo per character = ~$21,600/mo in pure digital product revenue

Layered on top of:
- Affiliate revenue ~ $30-50k/mo per character
- Subscribe & save book ~ $8-18k/mo per character
- Brand deals ~ $5-15k/mo per character

The digital layer adds $20-40k/mo to the network w zero marginal cost after the initial 2 hours of creating each PDF

(btw the digital products also serve as email list builders. Every buyer who purchases the $9 PDF gives u their email via gumroad/payhip. That email list becomes a second distribution channel the character owns forever, independent of any platform algorithm. If tiktok bans the page, the email list survives. If instagram changes the algorithm, the email list survives. 4,000 emails per character x 6 characters = 24,000 owned emails w a 38-44% open rate bc the audience opened the email to get the PDF they paid for.)

Sometimes the highest-margin product in the entire AI character economy is a 2-page google doc a 14yo could make in study hall + every operator on this app is too proud to sell it bc $9 doesn't look impressive on a screenshot...

The screenshot doesn't matter. The margin does.

link in bio if u want the digital product layer added to ur existing operation

or keep giving amazon 92% of ur commission while a $9 PDF pays u 100% lmfaooooo😂