Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Anthropic shipped 125 settings for Claude The official docs cover 40 One developer found the other 85 and his API bill dropped from $340 to $87 - not by using a cheaper model - not by writing shorter prompts just by moving one line in a config file to... the right place > memory scoped per project → past clients never bleed into new work > Extended Thinking on Light by default → 18–25% fewer Opus tokens in week one > cache_control moved to the right line → the fix that turned a $340 bill into $87 > plugins and MCP servers toggled off when idle → saved 25–40K tokens per session > per-project model override → Haiku for docs, Sonnet for infra, Opus only where it matters most Claude users are running a $100/month tool at 30% of its actual capabilityshow more

Shadow Nick

13,107 subscribers

380,456 views • 4 months ago •via X (Twitter)

Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Claude Code Head invented a word for what most config files aren't doing: tokenmaxxing. 90% of it lives in one place: ~/.claude/settings.json. 125 keys in v2.1.105. official docs cover 40. 4 of mine aren't anywhere in the docs. i audited the whole file - 18 settings actually decide what your month costs. > enabledPlugins - mine had 14 on, 4 actually used. each idle plugin loads hooks and SKILL.md at session start. > mcpServers.enabled - false instead of delete. 9 unused servers cost ~30K tokens of schema every session. > cache_control breakpoint at the static/dynamic boundary moved my Opus month from $340 to $87. tokenmaxxing isn't a vibe. it's a file with 125 keys most people never open. watch this tonight instead of the new Rick and Morty drop.

Claude Code Head invented a word for what most config files aren't doing: tokenmaxxing. 90% of it lives in one place: ~/.claude/settings.json. 125 keys in v2.1.105. official docs cover 40. 4 of mine aren't anywhere in the docs. i audited the whole file - 18 settings actually decide what your month costs. > enabledPlugins - mine had 14 on, 4 actually used. each idle plugin loads hooks and SKILL.md at session start. > mcpServers.enabled - false instead of delete. 9 unused servers cost ~30K tokens of schema every session. > cache_control breakpoint at the static/dynamic boundary moved my Opus month from $340 to $87. tokenmaxxing isn't a vibe. it's a file with 125 keys most people never open. watch this tonight instead of the new Rick and Morty drop.

Mnimiy

83,403 views • 4 months ago

ANTHROPIC LEAKED A SETUP THEY SPENT OVER 4 YEARS BUILDING WHERE A $30,000/MONTH TEAM GETS REPLACED BY $4 A DAY you're not a solo dev - you're one person carrying work the market prices at $30,000 a month. plan → code ×4 → tests → critic → docs → audit → back to the plan Opus cuts the task into steps and runs twice a day - the priciest model comes out at $1.05, not the biggest line on the bill. Sonnet holds 4 files at once across four lanes for $1.20 - the biggest line, and still the cheapest hour you ever bought. tests run themselves until green for $0.50 - you never see a red build again and never lose an hour to one. the critic is a different model than the one that wrote it - $0.72 for the only second pair of eyes a solo dev gets. $0.22 a day closes the docs you've been postponing for years - the cheapest role on the list turned out to be the one you skipped. the auditor at $0.32 closes the loop back into the planner - cut that edge and you get six assistants instead of a system. the left column is a hiring plan, the right column is a config file. save this and paste it into Claude Code - and you get 6 roles for $4 a day ↓

ANTHROPIC LEAKED A SETUP THEY SPENT OVER 4 YEARS BUILDING WHERE A $30,000/MONTH TEAM GETS REPLACED BY $4 A DAY you're not a solo dev - you're one person carrying work the market prices at $30,000 a month. plan → code ×4 → tests → critic → docs → audit → back to the plan Opus cuts the task into steps and runs twice a day - the priciest model comes out at $1.05, not the biggest line on the bill. Sonnet holds 4 files at once across four lanes for $1.20 - the biggest line, and still the cheapest hour you ever bought. tests run themselves until green for $0.50 - you never see a red build again and never lose an hour to one. the critic is a different model than the one that wrote it - $0.72 for the only second pair of eyes a solo dev gets. $0.22 a day closes the docs you've been postponing for years - the cheapest role on the list turned out to be the one you skipped. the auditor at $0.32 closes the loop back into the planner - cut that edge and you get six assistants instead of a system. the left column is a hiring plan, the right column is a config file. save this and paste it into Claude Code - and you get 6 roles for $4 a day ↓

Sprytix

13,699 views • 1 month ago

you handed a job to a subagent so your main window would stay clean the window stayed clean, the context did not tools load per conversation, not per task, so the browser tools you needed for one check sat in front of the model for everything you did after it four lines of frontmatter fix it, a subagent can carry its own servers, defined inline, scoped to that agent alone on my machine that moved twenty four playwright tools and four thousand four hundred tokens out of the main conversation and into the one place they get used you were not delegating work you were duplicating the menu and delegating a slice of it the cheapest tool is the one the model was never shown

you handed a job to a subagent so your main window would stay clean the window stayed clean, the context did not tools load per conversation, not per task, so the browser tools you needed for one check sat in front of the model for everything you did after it four lines of frontmatter fix it, a subagent can carry its own servers, defined inline, scoped to that agent alone on my machine that moved twenty four playwright tools and four thousand four hundred tokens out of the main conversation and into the one place they get used you were not delegating work you were duplicating the menu and delegating a slice of it the cheapest tool is the one the model was never shown

Lagosaur

42,020 views • 22 days ago

Jev’s founder just dropped the 12-page harness that makes coding agents 400× cheaper the first thing it shows: your agent spends under 10% of its tokens actually writing code → reading and searching take 56.2% of tool turns and 46.5% of tokens. that’s where the money goes → routing Opus → Sonnet → Opus to save costs 6.19. pure Opus costs 4.15. every handoff reprocesses the whole context → compress after the question, never before. every chunk gets scored: hide, short summary, long summary or full → instructions load by condition. touch *.tsx and the style guide loads. touch billing/ and its gotchas file loads. compaction can’t erase either → route by trust, not difficulty. secrets and infra stay on first-party frontier models, public docs go to the cheapest one → every command passes an allow / ask / deny policy that reads the script before it runs. not just its name their claim: 200× faster, 400× cheaper drop the PDF into Claude Code or Codex and let it rebuild your harness ↓

Jev’s founder just dropped the 12-page harness that makes coding agents 400× cheaper the first thing it shows: your agent spends under 10% of its tokens actually writing code → reading and searching take 56.2% of tool turns and 46.5% of tokens. that’s where the money goes → routing Opus → Sonnet → Opus to save costs 6.19. pure Opus costs 4.15. every handoff reprocesses the whole context → compress after the question, never before. every chunk gets scored: hide, short summary, long summary or full → instructions load by condition. touch *.tsx and the style guide loads. touch billing/ and its gotchas file loads. compaction can’t erase either → route by trust, not difficulty. secrets and infra stay on first-party frontier models, public docs go to the cheapest one → every command passes an allow / ask / deny policy that reads the script before it runs. not just its name their claim: 200× faster, 400× cheaper drop the PDF into Claude Code or Codex and let it rebuild your harness ↓

Carnage

61,361 views • 6 days ago

20-YEAR-OLD GUY SHOWS HOW CLAUDE API CAN TURN 500-VIEW CONTENT INTO A $40K/MONTH CLIENT WORKFLOW Not from a big agency. Not from hiring writers. Just taking the same service people sell every week and wiring Claude API into the boring middle. A topic goes in. It pulls the research, angles, outline, draft, edits, and a clean file. That is normally $500-$1,500 of freelance work per client project. The screen says around $40K/month, but the real number is the time saved. A $3K project stops being 8 hours of rewriting and becomes 45 minutes of checking before delivery. Most people use Claude to write one answer. He is showing what happens when the whole process becomes the product.

20-YEAR-OLD GUY SHOWS HOW CLAUDE API CAN TURN 500-VIEW CONTENT INTO A $40K/MONTH CLIENT WORKFLOW Not from a big agency. Not from hiring writers. Just taking the same service people sell every week and wiring Claude API into the boring middle. A topic goes in. It pulls the research, angles, outline, draft, edits, and a clean file. That is normally $500-$1,500 of freelance work per client project. The screen says around $40K/month, but the real number is the time saved. A $3K project stops being 8 hours of rewriting and becomes 45 minutes of checking before delivery. Most people use Claude to write one answer. He is showing what happens when the whole process becomes the product.

Gipp 🦅

19,254 views • 4 months ago

ANTHROPIC LEAKED A 3-SEAT SETUP WHERE THE BILL DROPS FROM $100 TO $21 AND SPEED GOES UP 3X engineers at Google and Microsoft have been running this for a while - they pay $21 where you pay $100. sorter → worker ×8 → judge → rejected → back to the worker every seat is a role you would otherwise have hired a person for - and none of the three adds headcount. Haiku throws 500 tasks a day into three buckets and doesn't think at all - anything you'd solve with a regex belongs on the cheapest seat. Sonnet carries the work across 8 parallel lanes 200 times a day - most of the bill lives right here. move this seat up one tier and the bill doubles with almost nothing to show for it. Opus runs only twice a day - expensive per turn and invisible on the bill. the author never grades its own work - Sonnet writes, Opus judges, rejected goes back. cut that judge to save money and you lose the only reason the cheap work is trusted. 3x isn't a faster model, it's eight lanes at once - you pay the latency of the slowest lane, not the sum of all. and the trap: 5x cheaper stops being true the second the cheap seat starts deciding. save this and paste it into Claude Code - and you get 3 seats instead of 3 hires ↓

ANTHROPIC LEAKED A 3-SEAT SETUP WHERE THE BILL DROPS FROM $100 TO $21 AND SPEED GOES UP 3X engineers at Google and Microsoft have been running this for a while - they pay $21 where you pay $100. sorter → worker ×8 → judge → rejected → back to the worker every seat is a role you would otherwise have hired a person for - and none of the three adds headcount. Haiku throws 500 tasks a day into three buckets and doesn't think at all - anything you'd solve with a regex belongs on the cheapest seat. Sonnet carries the work across 8 parallel lanes 200 times a day - most of the bill lives right here. move this seat up one tier and the bill doubles with almost nothing to show for it. Opus runs only twice a day - expensive per turn and invisible on the bill. the author never grades its own work - Sonnet writes, Opus judges, rejected goes back. cut that judge to save money and you lose the only reason the cheap work is trusted. 3x isn't a faster model, it's eight lanes at once - you pay the latency of the slowest lane, not the sum of all. and the trap: 5x cheaper stops being true the second the cheap seat starts deciding. save this and paste it into Claude Code - and you get 3 seats instead of 3 hires ↓

Sprytix

23,189 views • 1 month ago

Jev + Opus 5.5: Anthropic's new model beats GPT-6 Astra for 1/5 the cost, and 4 API changes will 400 your agent before it writes a single line I pulled these 10 steps from the migration docs so you don't learn them in production step 1 → $4 / $20 per 1M. Opus 5 was $5 / $25. cache reads dropped from $0.50 to $0.20 step 2 → 66.4% on Terminal-Bench 4.0 vs GPT-6 Astra 57.9% and Opus 5 52.3%. +14.1 points in one release, and on FrontierCode it beats Astra at default effort for 1/5 the cost step 3 → thinking can't be turned off anymore. send thinking: disabled and you get a 400. drop the field, set effort step 4 → tool_choice any and tool are gone. 400. switch to auto + strict step 5 → edit anything above a thinking block and the request dies. append only, or opt into drop_block step 6 → computer_20251124 is dead on the API. 400. move to computer_toolset_20260801 step 7 → the quiet one: default effort fell from high to medium. your agent thinks less than you set it up to and nothing tells you step 8 → hop Opus 5.5 → Sonnet 5 → Opus 5.5 and you pay 4.36 instead of 3.32. +31%, the cache dies and Sonnet can't read Opus's reasoning step 9 → change effort at the top of the request and the cache is gone. Jev sets it per message and the cache stays step 10 → switch fast - standard mid-session and it's a full cache miss. Jev picks speed once, on turn one one model, three knobs, zero 400s. that is Jev + Opus 5.5 send this to your Claude Code before you touch the model ID, then read my full Jev deep dive in the article below ↓

Jev + Opus 5.5: Anthropic's new model beats GPT-6 Astra for 1/5 the cost, and 4 API changes will 400 your agent before it writes a single line I pulled these 10 steps from the migration docs so you don't learn them in production step 1 → $4 / $20 per 1M. Opus 5 was $5 / $25. cache reads dropped from $0.50 to $0.20 step 2 → 66.4% on Terminal-Bench 4.0 vs GPT-6 Astra 57.9% and Opus 5 52.3%. +14.1 points in one release, and on FrontierCode it beats Astra at default effort for 1/5 the cost step 3 → thinking can't be turned off anymore. send thinking: disabled and you get a 400. drop the field, set effort step 4 → tool_choice any and tool are gone. 400. switch to auto + strict step 5 → edit anything above a thinking block and the request dies. append only, or opt into drop_block step 6 → computer_20251124 is dead on the API. 400. move to computer_toolset_20260801 step 7 → the quiet one: default effort fell from high to medium. your agent thinks less than you set it up to and nothing tells you step 8 → hop Opus 5.5 → Sonnet 5 → Opus 5.5 and you pay 4.36 instead of 3.32. +31%, the cache dies and Sonnet can't read Opus's reasoning step 9 → change effort at the top of the request and the cache is gone. Jev sets it per message and the cache stays step 10 → switch fast - standard mid-session and it's a full cache miss. Jev picks speed once, on turn one one model, three knobs, zero 400s. that is Jev + Opus 5.5 send this to your Claude Code before you touch the model ID, then read my full Jev deep dive in the article below ↓

Carnage

16,674 views • 5 days ago

ANTHROPIC LEAKED A 6-LOOP SETUP THAT REPLACES A $3,000 AGENCY AND COSTS $59 A MONTH Microsoft and Google have been running this for a while - the gap against an agency is exactly 51x. an agency charged you for waiting, not for work - the brief walked from the strategist to the copywriter to the designer for weeks. here all 6 loops read one file on the same pass - there's nobody to wait on, and the calendar is empty. 51% of the bill is production on Sonnet 5, and only 5% is strategy on Opus 5 - the priciest model runs once a week. 22% of the whole bill sits on the batch queue at half rate - where nobody is waiting for an answer right now. the journal is the only loop that writes back into the root - which angle is dead, and next week starts tighter. the 6 loops bring you 3 angles a week - the final pick stays yours, and that's the part that never automates. save this and paste it into Claude Code - the loops remove the waiting, not the judgement ↓

ANTHROPIC LEAKED A 6-LOOP SETUP THAT REPLACES A $3,000 AGENCY AND COSTS $59 A MONTH Microsoft and Google have been running this for a while - the gap against an agency is exactly 51x. an agency charged you for waiting, not for work - the brief walked from the strategist to the copywriter to the designer for weeks. here all 6 loops read one file on the same pass - there's nobody to wait on, and the calendar is empty. 51% of the bill is production on Sonnet 5, and only 5% is strategy on Opus 5 - the priciest model runs once a week. 22% of the whole bill sits on the batch queue at half rate - where nobody is waiting for an answer right now. the journal is the only loop that writes back into the root - which angle is dead, and next week starts tighter. the 6 loops bring you 3 angles a week - the final pick stays yours, and that's the part that never automates. save this and paste it into Claude Code - the loops remove the waiting, not the judgement ↓

Noisy

10,557 views • 1 month ago

ANTHROPIC LEAKED A $3.4M FILE THAT BUILDS AN AI BUSINESS AIMED AT $120K A MONTH IN 60 MINUTES AND COSTS $1.55 A DAY team of 5 costs $12,000 a month - this file costs $1.55 a day and never asks for a standup. the whole thing runs on one rule: the cheap model triages, the middle one builds, the expensive one decides. Opus 5 runs exactly once a day and is 13% of the bill - the priciest model is the smallest line on it. Sonnet 5 carries 3 parallel branches, and together with the hunt that's 81% of the entire bill. Haiku 4.5 reads 60 signals for pennies and hands back 12 letters - the block that used to eat your evenings now runs while you sleep. swap the models around and you get 5x overpaid, or a month of selling to nobody. the landing page, payment link, auto-replies and analytics get assembled at once in 12 minutes. 5 dashboards collapse into 3 numbers and one decision - and those numbers get written back into the root. $120K a month is either 400 customers at $300 or 1000 at $120 - and the price decides which of the two machines you built. the hour produces the machine, not the customers - it hunts just as hard even when nobody wants the product. save this and paste it into Claude Code - route by the cost of being wrong, not the price per token ↓

ANTHROPIC LEAKED A $3.4M FILE THAT BUILDS AN AI BUSINESS AIMED AT $120K A MONTH IN 60 MINUTES AND COSTS $1.55 A DAY team of 5 costs $12,000 a month - this file costs $1.55 a day and never asks for a standup. the whole thing runs on one rule: the cheap model triages, the middle one builds, the expensive one decides. Opus 5 runs exactly once a day and is 13% of the bill - the priciest model is the smallest line on it. Sonnet 5 carries 3 parallel branches, and together with the hunt that's 81% of the entire bill. Haiku 4.5 reads 60 signals for pennies and hands back 12 letters - the block that used to eat your evenings now runs while you sleep. swap the models around and you get 5x overpaid, or a month of selling to nobody. the landing page, payment link, auto-replies and analytics get assembled at once in 12 minutes. 5 dashboards collapse into 3 numbers and one decision - and those numbers get written back into the root. $120K a month is either 400 customers at $300 or 1000 at $120 - and the price decides which of the two machines you built. the hour produces the machine, not the customers - it hunts just as hard even when nobody wants the product. save this and paste it into Claude Code - route by the cost of being wrong, not the price per token ↓

Sprytix

29,960 views • 1 month ago

A developer in Hangzhou runs an AI that remembers everything about him for $0.40 a year. No vector database. One file that never grows past 4,000 tokens. He published the whole schema. His version starts from the opposite idea. Memory is not storage. It's a write policy. Six fields. Rewritten every time, never appended: > IDENTITY - who you are, what you build. 300 tokens. Changes monthly at most > STATE - what you're on right now. 400 tokens. Rewritten daily > DECISIONS - what's already settled, so nothing gets re-argued. 800 tokens > CORRECTIONS - every time you said "no, not like that." 600 tokens > PEOPLE - names, roles, who's waiting on what. 500 tokens > DEAD - tried and abandoned, so it never comes back as a suggestion. 400 tokens Three thousand tokens. Ceiling of four. When a section fills, the model rewrites it shorter. Nothing is ever added. Only replaced. Kimi K2.5 bills $0.10 per million cached input tokens. Four thousand tokens a turn is $0.0004. That's 2,500 turns for a dollar. The free tier hands you 1.5 million tokens a day. 375 turns before you pay anything at all. CORRECTIONS is the field nobody builds, and it's the one that does the work. A model that remembers being wrong stops repeating it. Everyone else is paying to search their own history. He pays to keep it short. The bill stopped growing when the file did. Your memory system isn't defined by what it stores. It's defined by what it agrees to delete. The article below is the full build - schema, rewrite prompts, the compaction rule that keeps it under the cap. Save it. You'll want it open in the other tab.

A developer in Hangzhou runs an AI that remembers everything about him for $0.40 a year. No vector database. One file that never grows past 4,000 tokens. He published the whole schema. His version starts from the opposite idea. Memory is not storage. It's a write policy. Six fields. Rewritten every time, never appended: > IDENTITY - who you are, what you build. 300 tokens. Changes monthly at most > STATE - what you're on right now. 400 tokens. Rewritten daily > DECISIONS - what's already settled, so nothing gets re-argued. 800 tokens > CORRECTIONS - every time you said "no, not like that." 600 tokens > PEOPLE - names, roles, who's waiting on what. 500 tokens > DEAD - tried and abandoned, so it never comes back as a suggestion. 400 tokens Three thousand tokens. Ceiling of four. When a section fills, the model rewrites it shorter. Nothing is ever added. Only replaced. Kimi K2.5 bills $0.10 per million cached input tokens. Four thousand tokens a turn is $0.0004. That's 2,500 turns for a dollar. The free tier hands you 1.5 million tokens a day. 375 turns before you pay anything at all. CORRECTIONS is the field nobody builds, and it's the one that does the work. A model that remembers being wrong stops repeating it. Everyone else is paying to search their own history. He pays to keep it short. The bill stopped growing when the file did. Your memory system isn't defined by what it stores. It's defined by what it agrees to delete. The article below is the full build - schema, rewrite prompts, the compaction rule that keeps it under the cap. Save it. You'll want it open in the other tab.

wast3

15,862 views • 1 month ago

Anthropic just gave OpenClaw the green light Anthropic staff confirmed that CLI-based usage is sanctioned. We’ve successfully bridged the Claude Code CLI directly into the OpenClaw gateway, letting you run your entire agent fleet on your Pro/Max plan and no additional API tokens required. The Implementation: - Auth: Log in to Claude Code locally: claude auth login - Path: Grab your binary location: which claude - Bridge: Drop the path into your openclaw.json under agents.defaults: "cliBackends": { "claude-cli": { "args": [ "-p", "--output-format", "json" ], "command": " ", "input": "arg", "output": "json", "serialize": true, "sessionArg": "--session-id", "sessionMode": "existing" } }, "model": { "primary": "claude-cli/claude-opus-4-6" }, "models": { "claude-cli/claude-opus-4-6": {}, "claude-cli/claude-opus-4-7": {}, "claude-cli/claude-sonnet-4-6": {} }, The Result: OpenClaw reuses your local session IDs and subscription limits. You get the full power of Opus and Sonnet without the restricted OAuth endpoints or the API tax. They sanctioned the path. We built the bridge. Here is a video how I done it step by step:

Anthropic just gave OpenClaw the green light Anthropic staff confirmed that CLI-based usage is sanctioned. We’ve successfully bridged the Claude Code CLI directly into the OpenClaw gateway, letting you run your entire agent fleet on your Pro/Max plan and no additional API tokens required. The Implementation: - Auth: Log in to Claude Code locally: claude auth login - Path: Grab your binary location: which claude - Bridge: Drop the path into your openclaw.json under agents.defaults: "cliBackends": { "claude-cli": { "args": [ "-p", "--output-format", "json" ], "command": " ", "input": "arg", "output": "json", "serialize": true, "sessionArg": "--session-id", "sessionMode": "existing" } }, "model": { "primary": "claude-cli/claude-opus-4-6" }, "models": { "claude-cli/claude-opus-4-6": {}, "claude-cli/claude-opus-4-7": {}, "claude-cli/claude-sonnet-4-6": {} }, The Result: OpenClaw reuses your local session IDs and subscription limits. You get the full power of Opus and Sonnet without the restricted OAuth endpoints or the API tax. They sanctioned the path. We built the bridge. Here is a video how I done it step by step:

Ziwen

184,184 views • 5 months ago

FREE Fable 5, Opus 4.8, Sonnet 5, and GPT-5.6 in one IDE. Alibaba built it, 520 credits at signup - one Sonnet 5 message eats 4. It's called Accio. Web or Windows desktop, both free. Registration takes 30 seconds via Google or email. Inside: → Fable 5 for creative and long-context work. → Opus 4.6 through 4.8 - the full Anthropic frontier lineup. → Sonnet 5 for speed and reasoning at pennies per message. → GPT-5.5 for OpenAI native tasks. → Gemini 3.1 Pro and 3.5 Flash for multimodal. Real math: 520 credits divided by 4 = 130 Sonnet 5 messages in your first week. Cheaper models drop that even further. Anthropic charges $20/month for the same access with weekly limits. Custom MCP support built in. Profile > Settings > MCP. Every agent workflow you've built for Claude Desktop ports over instantly. Setup: → Go to accio(.)com → Sign up with Google → 520 credits land automatically → Pick your model and start firing prompts Bookmark this before Alibaba puts it behind a paywall.

Atenov int.

31,157 views • 2 months ago

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

Gipp 🦅

10,799 views • 2 months ago

How to cut your AI bill by 60% switching to Opus 5.5: Most people will swap the model name, save 24%, and stop there. The other 37% is sitting in your settings. Here's the real before and after on an example agent workload. One month: 100M input tokens (80M cached reads, 5M cache writes, 15M uncached) 10M output tokens BEFORE: Opus 5 Cache reads: 80M × $0.50 = $40 Cache writes: 5M × $6.25 = $31.25 Uncached input: 15M × $5 = $75 Output: 10M × $25 = $250 Total: $396.25 STEP 1. Just switch the model. Same tokens, new prices. Cache reads $0.20. Writes $5. Input $4. Output $20. $16 + $25 + $60 + $200 = $301 24% cheaper. That's what everyone's screenshotting. STEP 2. Let it write less. Box measured Opus 5.5 at 40% less verbose with no drop in accuracy. 10M output tokens becomes 6M. Output drops from $200 to $120. Total: $221. Now you're at 44% off. STEP 3. Stop running every call at max effort. Thinking can't be switched off on 5.5 anymore, so effort is your lever. Classifying, routing, formatting, summarizing? Drop the effort. Save the high settings for the calls that actually reason. Say that trims output another 25%, 6M down to 4.5M. Output: $90. Total: $191. 52% off. STEP 4. Cache the stuff you keep resending. This is the one nobody does. Cache reads went from $0.50 to $0.20. That's 60% off the cheapest line on your bill. Move your system prompt, tool definitions and repo context into the cache. Uncached input drops from 15M to 5M, cache reads go up to 90M. $18 + $25 + $20 + $90 = $153 AFTER: $153 From $396.25. 61% cheaper. Same work. The model gave you 24%. You gave yourself the other 37%. Anthropic's own number is 40% cheaper than Opus 5 on typical workloads. Your number depends on how much of your bill is output and how much of your prompt you're resending uncached every call. So check those two first. Bookmark this for when you migrate. follow CyrilXBT

How to cut your AI bill by 60% switching to Opus 5.5: Most people will swap the model name, save 24%, and stop there. The other 37% is sitting in your settings. Here's the real before and after on an example agent workload. One month: 100M input tokens (80M cached reads, 5M cache writes, 15M uncached) 10M output tokens BEFORE: Opus 5 Cache reads: 80M × $0.50 = $40 Cache writes: 5M × $6.25 = $31.25 Uncached input: 15M × $5 = $75 Output: 10M × $25 = $250 Total: $396.25 STEP 1. Just switch the model. Same tokens, new prices. Cache reads $0.20. Writes $5. Input $4. Output $20. $16 + $25 + $60 + $200 = $301 24% cheaper. That's what everyone's screenshotting. STEP 2. Let it write less. Box measured Opus 5.5 at 40% less verbose with no drop in accuracy. 10M output tokens becomes 6M. Output drops from $200 to $120. Total: $221. Now you're at 44% off. STEP 3. Stop running every call at max effort. Thinking can't be switched off on 5.5 anymore, so effort is your lever. Classifying, routing, formatting, summarizing? Drop the effort. Save the high settings for the calls that actually reason. Say that trims output another 25%, 6M down to 4.5M. Output: $90. Total: $191. 52% off. STEP 4. Cache the stuff you keep resending. This is the one nobody does. Cache reads went from $0.50 to $0.20. That's 60% off the cheapest line on your bill. Move your system prompt, tool definitions and repo context into the cache. Uncached input drops from 15M to 5M, cache reads go up to 90M. $18 + $25 + $20 + $90 = $153 AFTER: $153 From $396.25. 61% cheaper. Same work. The model gave you 24%. You gave yourself the other 37%. Anthropic's own number is 40% cheaper than Opus 5 on typical workloads. Your number depends on how much of your bill is output and how much of your prompt you're resending uncached every call. So check those two first. Bookmark this for when you migrate. follow CyrilXBT

CyrilXBT

15,803 views • 4 days ago

ANTHROPIC LEAKED A FILE WHERE 4 DEPARTMENTS ASSEMBLE IN 60 MINUTES AND BUILD A BUSINESS THAT MAKES $100K A MONTH the same work done by people is $30,000 a month - here it's 4 departments and $2.65 a day. the first 12 minutes you write 3 lines all 4 departments will read all week: who buys, what we sell, at what price. development is the largest line on the bill - $1.30, three cheap lanes in parallel and one expensive verdict at the end. marketing is high volume with a low stake per item - so it generates 3 variants and you pick one. one variant is a guess, three variants are a choice, and they cost the same. research runs the other way: the cheap model filters hundreds of sources, the expensive one reads only what survived. paying the top rate for a page you'll discard anyway is the commonest overspend there is. and there's exactly one department where saving on the model makes no sense - unit economics: one wrong number costs you a year. route by the cost of being wrong, not the price per token - Opus on the content queue is 5x overpaid, Haiku on the economics is a year of rework. finance is the only department that writes back into the root - next week marketing runs on rules the economics wrote. at minute 60 you have a page, a payment link, a week of content and an economics model - revenue isn't on that list. save this and paste it into Claude Code - the hour builds the company, the market decides the number ↓

ANTHROPIC LEAKED A FILE WHERE 4 DEPARTMENTS ASSEMBLE IN 60 MINUTES AND BUILD A BUSINESS THAT MAKES $100K A MONTH the same work done by people is $30,000 a month - here it's 4 departments and $2.65 a day. the first 12 minutes you write 3 lines all 4 departments will read all week: who buys, what we sell, at what price. development is the largest line on the bill - $1.30, three cheap lanes in parallel and one expensive verdict at the end. marketing is high volume with a low stake per item - so it generates 3 variants and you pick one. one variant is a guess, three variants are a choice, and they cost the same. research runs the other way: the cheap model filters hundreds of sources, the expensive one reads only what survived. paying the top rate for a page you'll discard anyway is the commonest overspend there is. and there's exactly one department where saving on the model makes no sense - unit economics: one wrong number costs you a year. route by the cost of being wrong, not the price per token - Opus on the content queue is 5x overpaid, Haiku on the economics is a year of rework. finance is the only department that writes back into the root - next week marketing runs on rules the economics wrote. at minute 60 you have a page, a payment link, a week of content and an economics model - revenue isn't on that list. save this and paste it into Claude Code - the hour builds the company, the market decides the number ↓

Sprytix

19,325 views • 1 month ago

ANTHROPIC LEAKED A SETUP WHERE A $1.2M A-YEAR TEAM FITS INTO ONE FILE FOR $4 A DAY you hire nobody - you write one file, and $106,500 of salaries in it turn into $4 of tokens. architect → 4 builders → tests → critic → docs → scout → chief → back into the file the architect runs twice a day and decides everything - the priciest model on the sheet is the smallest line on the bill at $1.05. four builders cost $1.20 a day - and a fifth builder is one more number in the file, not one more quarter of recruiting. the tester asks does it run, the critic asks should it exist at all - $1.22 together for two roles a solo dev never fills. nothing reaches you that hasn't been rejected at least once. the scout and the scribe cost 40 cents - the exact two roles that get cut from every real budget. nobody hires a documentation engineer, and everybody wishes they had one. the chief at 14 cents is the only one who writes back into the file - without it this is a list, with it the list edits itself. hiring the eleventh is a paragraph: no req, no interviews, no ramp - and firing is one command. save this and paste it into Claude Code - and you get 10 roles for the price of one coffee ↓

ANTHROPIC LEAKED A SETUP WHERE A $1.2M A-YEAR TEAM FITS INTO ONE FILE FOR $4 A DAY you hire nobody - you write one file, and $106,500 of salaries in it turn into $4 of tokens. architect → 4 builders → tests → critic → docs → scout → chief → back into the file the architect runs twice a day and decides everything - the priciest model on the sheet is the smallest line on the bill at $1.05. four builders cost $1.20 a day - and a fifth builder is one more number in the file, not one more quarter of recruiting. the tester asks does it run, the critic asks should it exist at all - $1.22 together for two roles a solo dev never fills. nothing reaches you that hasn't been rejected at least once. the scout and the scribe cost 40 cents - the exact two roles that get cut from every real budget. nobody hires a documentation engineer, and everybody wishes they had one. the chief at 14 cents is the only one who writes back into the file - without it this is a list, with it the list edits itself. hiring the eleventh is a paragraph: no req, no interviews, no ramp - and firing is one command. save this and paste it into Claude Code - and you get 10 roles for the price of one coffee ↓

Sprytix

47,679 views • 1 month ago

10 repos that cut your ai agent token bill by up to 80% 1. microsoft/LLMLingua → cuts prompt size by up to 95% compresses prompts before the api call. 20x compression. published at EMNLP + ACL. near-zero quality loss. 6,100 stars 2. mem0ai/mem0 → replaces full conversation history in context stores what matters. retrieves only what's needed. 10,000 token history → 200 token memory. per agent. 54,800 stars 3. BerriAI/litellm → routes each call to the cheapest model simple task → haiku. complex task → sonnet. tracks cost per agent, per call, per day. 45,700 stars 4. run-llama/llama_index → replaces sending full documents rag: 100-page doc → 3 relevant chunks → same answer. 98% fewer tokens per query. 49,100 stars 5. chroma-core/chroma → replaces keyword search in full context vector store. finds the closest match. feeds only that. 50-200 tokens per query instead of thousands. 27,800 stars 6. letta-ai/letta → replaces infinite context window crashes paged memory for agents. loads only relevant memory. stops your agent from hitting limits and retrying. 22,400 stars 7. guidance-ai/guidance → cuts output token bloat by 30-50% structured generation. constrains model output natively. no more 100-token prompts to get json back. 21,400 stars 8. Aider-AI/aider → replaces pasting entire codebases builds a repo map. sends only files relevant to the task. not your whole project. just what the agent needs. 44,300 stars 9. openai/tiktoken → count tokens before you send know the exact cost before the api call happens. not after the bill arrives. 18,100 stars 10. simonw/ttok → hard cap on what gets sent cli tool: count tokens, truncate to budget limit. pipe any text in. get truncated output back. 389 stars most agents are expensive not because the model is expensive. because nobody checked what was being sent to it.

10 repos that cut your ai agent token bill by up to 80% 1. microsoft/LLMLingua → cuts prompt size by up to 95% compresses prompts before the api call. 20x compression. published at EMNLP + ACL. near-zero quality loss. 6,100 stars 2. mem0ai/mem0 → replaces full conversation history in context stores what matters. retrieves only what's needed. 10,000 token history → 200 token memory. per agent. 54,800 stars 3. BerriAI/litellm → routes each call to the cheapest model simple task → haiku. complex task → sonnet. tracks cost per agent, per call, per day. 45,700 stars 4. run-llama/llama_index → replaces sending full documents rag: 100-page doc → 3 relevant chunks → same answer. 98% fewer tokens per query. 49,100 stars 5. chroma-core/chroma → replaces keyword search in full context vector store. finds the closest match. feeds only that. 50-200 tokens per query instead of thousands. 27,800 stars 6. letta-ai/letta → replaces infinite context window crashes paged memory for agents. loads only relevant memory. stops your agent from hitting limits and retrying. 22,400 stars 7. guidance-ai/guidance → cuts output token bloat by 30-50% structured generation. constrains model output natively. no more 100-token prompts to get json back. 21,400 stars 8. Aider-AI/aider → replaces pasting entire codebases builds a repo map. sends only files relevant to the task. not your whole project. just what the agent needs. 44,300 stars 9. openai/tiktoken → count tokens before you send know the exact cost before the api call happens. not after the bill arrives. 18,100 stars 10. simonw/ttok → hard cap on what gets sent cli tool: count tokens, truncate to budget limit. pipe any text in. get truncated output back. 389 stars most agents are expensive not because the model is expensive. because nobody checked what was being sent to it.

self.dll

39,554 views • 4 months ago

This guy replaced an $8,000 survey crew with one drone and a pipeline on Claude Code that digitizes a whole site in a single trip. Inside it is not one drone but a whole pipeline of 5 modules on Claude Code each with its own job all answering to a single orchestrator. And he built them himself with no team. He draws one line on the map from the controller and the whole site starts turning into data at once. Pilot flies the DJI Matrice 350 RTK along the route and reaches where a crew drags tripods: the parking lot and the roofs and the grading. Scanner on the Zenmuse L2 records the geometry with a laser down to the centimeter. Builder in DJI Terra stitches the point cloud into a digital twin. Analyst on Claude builds what the client needs out of the finished model: a volume report and a progress diff and a tour behind a link. Mobile lives in his iPhone and hands the developer a link to the model while he drives to the next site. The site is ready as a file in about an hour and the developer rotates it in the browser himself and measures distances. No crew. No tripods. No week on site. Just him and a pickup and a drone and one API key. The whole processing pipeline lives in a folder at /Users/dev/site-capture. But he did not stop at a one time scan. The pipeline raises him by voice only when a flight misses a patch or when a sag on site goes past tolerance. And this is not made up: the DJI Matrice 350 RTK and the Zenmuse L2 are off the shelf enterprise hardware. The specs are one search away and the L2 really does write around 240,000 points per second. A crew for the same job charges $8,000 and three trips plus a week of desk work. His cost is tokens and subscriptions: one battery charge per flight and around $300 a month to host the finished models. In the end he draws one line on the map and an operator that does not exist scans the site and calculates the volumes and builds the report while he never leaves his truck. There is a huge market of everyone who needs to measure construction sites and warehouses and roofs and parking lots over and over while they still send out a photographer with a camera and wait a week. And he built this whole pipeline himself: one drone and one scanner and Claude Code that turns a flight into a file the developer pays for.

This guy replaced an $8,000 survey crew with one drone and a pipeline on Claude Code that digitizes a whole site in a single trip. Inside it is not one drone but a whole pipeline of 5 modules on Claude Code each with its own job all answering to a single orchestrator. And he built them himself with no team. He draws one line on the map from the controller and the whole site starts turning into data at once. Pilot flies the DJI Matrice 350 RTK along the route and reaches where a crew drags tripods: the parking lot and the roofs and the grading. Scanner on the Zenmuse L2 records the geometry with a laser down to the centimeter. Builder in DJI Terra stitches the point cloud into a digital twin. Analyst on Claude builds what the client needs out of the finished model: a volume report and a progress diff and a tour behind a link. Mobile lives in his iPhone and hands the developer a link to the model while he drives to the next site. The site is ready as a file in about an hour and the developer rotates it in the browser himself and measures distances. No crew. No tripods. No week on site. Just him and a pickup and a drone and one API key. The whole processing pipeline lives in a folder at /Users/dev/site-capture. But he did not stop at a one time scan. The pipeline raises him by voice only when a flight misses a patch or when a sag on site goes past tolerance. And this is not made up: the DJI Matrice 350 RTK and the Zenmuse L2 are off the shelf enterprise hardware. The specs are one search away and the L2 really does write around 240,000 points per second. A crew for the same job charges $8,000 and three trips plus a week of desk work. His cost is tokens and subscriptions: one battery charge per flight and around $300 a month to host the finished models. In the end he draws one line on the map and an operator that does not exist scans the site and calculates the volumes and builds the report while he never leaves his truck. There is a huge market of everyone who needs to measure construction sites and warehouses and roofs and parking lots over and over while they still send out a photographer with a camera and wait a week. And he built this whole pipeline himself: one drone and one scanner and Claude Code that turns a flight into a file the developer pays for.

Blaze

10,772 views • 3 months ago

SOMEONE IS CHARGING $5,000/MONTH FOR SOCIAL MEDIA CONTENT THAT CLAUDE WRITES IN 6 HOURS A WEEK no team, no office, just Claude and a scheduling app mid-market companies pay $2,000-$5,000 per month for social media management, and most of them are getting a junior freelancer posting generic content or an agency that barely touches their account one of them runs the whole thing in a weekly workflow: brief Claude on Monday, write posts Tuesday and Wednesday, schedule Thursday, pull numbers Friday another one charged three clients the same $5,000 rate before hiring a single person, that's $180,000/year running on one tool there's a prompt that makes Claude write every post in the client's exact voice by analyzing 5 examples of their existing content, 10 min per post instead of 60 you can land the first client with one outreach message, no portfolio, no case studies, just a specific offer and a 30-minute call the model is already working, the only question is whether you build it or watch someone else do it full breakdown of the workflow, the prompts, and how to find clients in the article below

SOMEONE IS CHARGING $5,000/MONTH FOR SOCIAL MEDIA CONTENT THAT CLAUDE WRITES IN 6 HOURS A WEEK no team, no office, just Claude and a scheduling app mid-market companies pay $2,000-$5,000 per month for social media management, and most of them are getting a junior freelancer posting generic content or an agency that barely touches their account one of them runs the whole thing in a weekly workflow: brief Claude on Monday, write posts Tuesday and Wednesday, schedule Thursday, pull numbers Friday another one charged three clients the same $5,000 rate before hiring a single person, that's $180,000/year running on one tool there's a prompt that makes Claude write every post in the client's exact voice by analyzing 5 examples of their existing content, 10 min per post instead of 60 you can land the first client with one outreach message, no portfolio, no case studies, just a specific offer and a 30-minute call the model is already working, the only question is whether you build it or watch someone else do it full breakdown of the workflow, the prompts, and how to find clients in the article below

Chrome

13,769 views • 4 months ago

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

Gipp 🦅

14,871 views • 4 months ago