08:31Brad | AI & Automation · Tutorial
This Skill Can INSTANTLY Watch any Video For Free — Here's How
A Claude Code plugin update that makes an AI watch any video 40 times faster by grabbing keyframes instead of decoding every frame.
July 2ndThe argument in one line.
Six free configuration habits — model selection, CLAUDE.md, Plan Mode, context compaction, .claudeignore, and idle MCP pruning — separate Claude Code users who burn through credits in days from those who run the same workload at half the cost.
Read if. Skip if.
READ IF YOU ARE…
- You use Claude Code regularly and credit burn feels disproportionate to what you actually shipped.
- You are a freelancer, agency owner, or solo builder using Claude Code for client work and want predictable costs.
- You are new to Claude Code and want to establish correct defaults before bad habits compound.
- You manage a small team on Claude Code and want sensible session hygiene before per-developer costs scale.
SKIP IF…
- You already use /model, CLAUDE.md, Plan Mode, and .claudeignore as standard practice — this will not surprise you.
- You want advanced architectural or prompt engineering guidance; this is entry-level setup optimization.
The full version, fast.
Claude Code's defaults are optimized for capability, not cost — it ships with Opus as the default model, starts every session context-blind, and silently loads massive directory trees and idle MCP tool definitions before you type a word. Six habits address every major leak: use Sonnet as the default and escalate to Opus only when reasoning demands it; write a CLAUDE.md under 200 lines so the agent arrives oriented; engage Plan Mode before execution on complex tasks; run /compact every 15 minutes to keep history lean; add a .claudeignore to block node_modules and build artifacts; and disconnect MCP servers not used that week. Together these eliminate the largest sources of unnecessary token spend without touching real capability.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 00:56
01 · Hook + channel intro
Pain-point mirror open: credits gone, no idea why. Promise: 5 setup steps nobody talks about. AI avatar disclosure and masterclass pre-sell.
00:57 – 02:43
02 · What Claude Code is and why setup costs money
Quick primer on Claude Code as an agentic coding tool. Growth stats: $1B ARR in 6 months. Poor habits cost $13/developer/day ($150-$250/month).
02:44 – 03:43
03 · Mistake #1: Running Opus for everything
Claude Code defaults to Opus. Model tier breakdown: Haiku (simple), Sonnet (bulk work), Opus (complex reasoning). Switching to Sonnet saves ~60% tokens.
03:44 – 04:26
04 · Mistake #2: No CLAUDE.md file
Without CLAUDE.md, every session re-explains the whole project. One file under 200 lines gives Claude persistent context. One-hour setup, perpetual savings.
04:27 – 05:01
05 · Mistake #3: Building without Plan Mode
80/20 workflow: 80% planning in Plan Mode, 20% execution. Plan Mode reads codebase first, proposes a plan before touching files. 50-70% token reduction on complex tasks.
05:02 – 05:43
06 · Mid-roll: AI Cashflow Masterclass
Sponsored segment promoting free on-demand training on using AI workflows for income.
05:44 – 06:33
07 · Mistake #4: Context window overload
Every message resends full history. /compact compresses, /clear resets, /usage tracks spend in real time. Run /compact every 15 minutes, not at 95% full.
06:34 – 07:07
08 · Mistake #5: No .claudeignore
.claudeignore blocks node_modules, build folders, lock files from being read. One setup, 80-90% exploration waste cut on medium projects.
07:08 – 07:37
09 · Bonus: Idle MCP servers
Each connected MCP server loads full tool definitions into context even when unused. One idle server = 14,000+ tokens before work starts. Run /mcp and disconnect unused servers.
07:38 – 08:25
10 · The bigger picture
This is not just for developers. Freelancers, agency owners, entrepreneurs using Claude Code correctly have a genuine competitive advantage.
08:26 – 09:36
11 · Recap + final CTA
All 6 habits restated. Every one is free to set up. Final masterclass pitch with 30-day HighLevel trial offer.
Lines worth screenshotting.
- Claude Code defaults to Opus for every task, even renaming a file or fixing a typo.
- Switching to Sonnet as the default and escalating to Opus only when needed cuts token usage by roughly 60% with no real capability loss.
- Poor Claude Code setup habits cost approximately $13 per developer per active day, or $150-$250 per developer per month.
- A CLAUDE.md file under 200 lines gives the agent your full project context before a single prompt token is spent on orientation.
- Anthropic's own documentation caps CLAUDE.md at 200 lines — exceeding it degrades rule adherence and triggers compliance decay.
- Plan Mode reads the codebase and proposes a full plan before touching any file, cutting token costs on complex tasks by 50-70%.
- The 80/20 workflow — 80% planning in Plan Mode, 20% execution — is how the developers with the lowest token bills actually work.
- Every message in a long Claude Code session carries the full conversation history, making sessions exponentially more expensive over time.
- Running /compact every 15 minutes compresses history without losing context; waiting for the 95% auto-compact means you have already overpaid.
- A .claudeignore file blocks node_modules, build folders, and lock files — on a medium project this cuts exploration waste by 80-90%.
- One idle MCP server with its tool definitions loaded silently consumes over 14,000 tokens per session before you type a single word.
- Auditing connected MCP servers weekly with /mcp and disconnecting unused ones is one of the highest-leverage, lowest-effort cost habits.
- The video is narrated entirely by an AI avatar of the host — the real person does not appear on camera.
Six habits that cut Claude Code costs in half.
WHAT TO LEARN
The default Claude Code install is optimized for capability, not cost — six free configuration steps fix the biggest leaks before they compound.
- Claude Code defaults to Opus for every task regardless of complexity; switching to Sonnet for routine work and escalating only for hard reasoning cuts token usage by roughly 60%.
- A CLAUDE.md file under 200 lines eliminates the per-session cost of re-explaining your project stack and rules — once written it saves tokens on every future session.
- Plan Mode forces the agent to read the codebase and propose a full plan before touching any file; skipping it means paying for failed attempts and do-overs on complex tasks.
- Every new message in a session carries the full conversation history; running /compact every 15 minutes keeps context lean rather than waiting for the 95% auto-compact threshold.
- A .claudeignore file prevents the agent from reading node_modules, build folders, and lock files — directories that can be massive and are almost never relevant to the actual task.
- Each connected MCP server loads its entire tool definition list into context even when idle; one unused server can consume over 14,000 tokens per session before any real work begins.
- The total cost reduction from applying all six habits compounds — model savings, context savings, and exploration savings each reduce the base the next one operates on.
Terms worth knowing.
- Opus
- Anthropic's most capable and most expensive Claude model tier, suited for complex multi-file reasoning and hard architectural decisions — overkill for routine coding tasks.
- Sonnet
- The mid-tier Claude model — significantly cheaper than Opus and sufficient for the vast majority of everyday coding work including writing functions, refactoring, and adding features.
- Haiku
- The fastest and cheapest Claude model tier, best suited for simple tasks like renaming files, fixing typos, or writing basic boilerplate.
- CLAUDE.md
- A markdown file placed in a project folder that Claude Code reads at the start of every session, providing persistent context about the stack, architecture, and rules without consuming per-message tokens.
- Plan Mode
- A Claude Code mode that reads the codebase and generates a full implementation plan for review before executing any file changes, reducing failed attempts and costly do-overs.
- /compact
- A Claude Code slash command that compresses the current session's conversation history to reduce context size and token cost while preserving important context.
- .claudeignore
- A file analogous to .gitignore that tells Claude Code which directories and file types to skip entirely during exploration, most commonly used to exclude node_modules and build artifacts.
- MCP server
- Model Context Protocol servers are external tool integrations connected to Claude Code; each one loads its full tool definitions into context even when idle, consuming tokens before any work begins.
- Context window
- The total amount of text (measured in tokens) that an AI model can process at once in a single session; in Claude Code, every new message resends the entire conversation history, making long sessions progressively more expensive.
- Token
- The unit Claude uses for billing; roughly 3-4 characters of text. Input and output tokens are priced separately, and cached input tokens cost about 10% of fresh input tokens.
Things they pointed at.
01:46linkBuilt In: Claude Code Puts Tech Workers on Notice
01:52linkAnthropic blog: Claude Code reaches $1B milestone
Lines you could clip.
00:11
“It wasn't the tool. It was the setup.”
06:07
“It's like packing for a weekend trip but dragging your entire house with you.”
07:20
“One unused MCP server can silently eat over 14,000 tokens per session before you've typed a single word.”
04:08
“With a clean Claude.md in place, Claude already knows everything before you type a single word.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphoranalogy
You downloaded Clogcode. You fired it up. You got excited.
You started building. And then three days later, your credits were gone, and you had no idea why. Here's the thing.
It wasn't the tool. It was the setup. Most people skip five steps right after the install that quietly drain credits in the background every single session.
Nobody talks about them. Today, I'm gonna walk you through each one, show you exactly why they matter, and explain how fixing them could save you a lot of money and a lot of frustration. Stay right here because this is actually the video you needed before you ever typed single command.
Let's get into it. Hey there. I'm Nick Ponte's AI avatar.
While the real Nick is busy helping businesses with Mina Marketing, Hawaii's fastest growing marketing agency, I'm here dropping the latest AI hacks, tools, and money making strategies. The Real Nick reads every single comment on these videos, so make sure you comment below. And, hey, if you're serious about landing some AI subscription based customers, grab my AI cash flow masterclass that I'm currently offering for free.
The link's in the description. Alright. Now let's get into it.
When I first started getting into AI tools, I made a lot of mistakes. I picked the wrong things, wasted time, and learned the hard way more often than I'd like to admit. That's actually why I know this stuff well now.
I've already burned through the credits, you don't have to. Today, you get to skip all that trial and error and jump straight to what actually works.
Alright. Let's get on the same page quick. Claude Code isn't just another chatbot.
It's a full AI coding agent built by Anthropic. You give it a task, it actually goes into your project, reads your files, makes changes, runs tests, and builds things from start to finish.
Think of it as , never gets tired, never misses a deadline, and doesn't need you to explain the same thing twice. Now before you think this is just for developers, stick with me because this directly affects how you make money online right now. Here's how fast this thing has taken off.
Claude Code launched publicly in May 2025 and hit $1,000,000,000 in annualized revenue in just six months. That's faster growth than any enterprise software product in history.
By early twenty twenty six, that number had already more than doubled. Companies like Netflix, Spotify, and Salesforce are all using it. This isn't some niche developer toy anymore.
It's becoming the standard way serious people build and automate things.
Here's where it gets interesting. Most people install Claude code and immediately jump straight into asking it to build things. And it works for a while.
Then the credits start disappearing way faster than expected. Output quality drops, and people end up blaming the tool. The real issue is almost always the same thing, the setup.
One breakdown of average Claude code usage found that poor habits can push your cost to around $13 per developer per active day. Multiply that out across a full month, and you're sitting somewhere between 150 and over $250.
And that's before the really expensive mistakes even kick in. Let me show you exactly what those mistakes are.
This is the biggest one, and almost nobody's talking about it. Claude code defaults to Opus, which is the most powerful and most expensive model available. The truth is the vast majority of everyday tasks don't need Opus at all.
Here's a simple way to think about it. Haiku handles the simple stuff. Renaming a file, fixing a typo, writing basic boilerplate.
Cheap and fast. Sonnet handles the bulk of real coding work. Writing functions, refactoring, adding features.
Powerful, but way more affordable. Opus is for the heavy lifting, complex architecture, tricky multi file reasoning, bugs that nothing else can crack. The mistake most people make is leaving Claude code on Opus for literally everything.
You can switch models in the terminal by typing slash model sonnet or slash model haiku. Starting every session on Sonnet and only stepping up to Opus when you genuinely need it can cut your token usage by around 60% without losing any real capability. That's real money staying in your pocket every single month.
This is the step that separates the people who really get it from everyone else. Claude dot m d is a simple markdown file that lives in your project folder. Claude code reads it at the start of every single session.
It's your instruction sheet. Without it, you're explaining your entire project from scratch every time. What language you're using, what's in your stack, how you want things structured.
Every session, every time. All those repeated explanations cost tokens. Tokens cost money.
With a clean Claude dot m d in place, Claude already knows everything before you type a single word. Anthropics' own documentation officially recommends keeping it under 200 lines. Just your stack, your rules, and your architecture.
Nothing extra. It takes an hour to set up, and it saves you credits on every session after that forever.
Most people open Claude code and immediately tell it to start building. Claude gets going. It writes code.
It moves fast. And then halfway through, something goes sideways, and suddenly you're spending a ton of tokens fixing work that should have been right from the start. Plan mode is the fix.
When you activate it, Claude reads your code base first and proposes a full plan before touching a single file. You review it. You tweak anything you want.
You approve it. Only then does it execute. The developers who've cracked this follow what's called an eighty twenty workflow.
80% planning, 20% execution. Research on plan mode found it can cut your total token cost on complex tasks by 50 to 70% just by eliminating failed attempts and costly do overs.
You're not doing less work. You're doing it smarter. If you've been watching this and thinking, okay.
This AI stuff makes sense. But how do I actually turn it into real income? That's exactly what my free AI cash flow masterclass is all about.
It's not theory. It's a step by step breakdown of how people are using simple AI workflows right now to create real income online. You'll see the exact types of services businesses are already paying for, workflows you can set up without any coding background, and how to find businesses that already know they're behind on AI and are ready to pay for help.
We call that AI guilt, and it's everywhere. The link is in the description and pinned in the top comment. Check it out and come right back because we've still got more ground to cover.
Here's one that quietly kills sessions and nobody warns you about it. Every message you send in Claude code carries your entire conversation history along with it. Every response, every file Claude looked at, all of it gets resent with every new message.
So the longer a session runs, the heavier and more expensive it gets. It's like packing for a weekend trip but dragging your entire house with you. The fix is simple.
Slash compact compresses your conversation history without losing the important context. Slash clear wipes it clean and starts fresh. Slash usage shows you exactly how many tokens you've spent in real time.
Experts recommend running slash compact every fifteen minutes or so during long sessions. Don't wait for Claude to auto compact at 95% full.
By that point, you've already been overpaying for context you didn't need.
This one is sneaky. When you're working inside a project folder, Claude code will sometimes explore files it never needed to touch. Build folders, lock files, node modules.
These are massive. And if you don't block them, Claude reads them anyway, and that burns tokens fast. A dot Claude ignore file works exactly like a dot git ignore.
You list the folders and file types you want Claude to skip, and it skips them completely. On a medium sized project, this single step alone can cut exploration waste by 80 to 90%. It takes five minutes to create.
You set it up once, and it pays you back on every single session after that.
Here's one more that goes a level deeper. MCP servers are external tools and connections you can plug into Claude code. They're powerful when you actually use them.
But even when they're just sitting there idle, each connected server adds its full tool definitions to your context. One unused MCP server can silently eat over 14,000 tokens per session before you've typed a single word.
Run slash MCP in your terminal. See what's connected. If you haven't used something this week, turn it off.
This one habit makes a real difference across every single session going forward.
Look. I know a lot of people watching this aren't developers. And honestly, that's perfectly fine because this isn't really about coding.
It's about building things that people pay for. And here's what's actually exciting about that. ClaudeCode is being used by freelancers, agency owners, and entrepreneurs to build real things, automations, internal tools, client facing products, and entire services from scratch.
Things that used to require hiring a full time developer are now things regular people can build, own, and sell. That's a real shift. And if you know how to set it up correctly, which is exactly what we just walked through together, you're already ahead of most people out there who are burning through credits and quitting before anything meaningful ever gets built.
The people who understand the setup are the ones who actually get to use this tool as a real competitive advantage. And right now, that matters a lot.
Alright. Quick recap before we wrap this thing up. Switch to Sonnet as your default model and only go up to Opus when something genuinely needs it.
Set up your claude.md file before you start any new project. Use plan mode before you build anything complex.
Run slash compact regularly during long sessions. Create a dot claud ignore in every project folder, and disconnect any MCP servers you're not actively using. Those six habits are the actual difference between a tool that quietly drains your budget month after month and one that genuinely helps you build things fast and efficiently.
And the cool part is every single one of them is free to set up. And if you're ready to take this further and learn how to turn AI workflows into actual income streams, my free AI cash flow masterclass is where that journey starts.
It covers the exact services businesses are paying for right now, how to find clients who already want help and are ready to pay, and how to use the right AI software to run the whole thing. There's even a free thirty day trial of the platform I personally use to run my agency and land clients built right into the master class.
People who are getting into this now are the ones who are going to be ahead when everyone else catches on. The link is in the description. Don't wait on it.
I'll see you in the next one.
The Hook
The bait, then the rug-pull.
Three days after install, the credits are gone and you have no idea why. That gap between excited first build and confusing budget drain is exactly what this video fills — not with more features, but with six setup steps that should have come before the first prompt.
Named ideas worth stealing.
08:26list
The 6-Habit Claude Code Setup
- Use Sonnet as default; escalate to Opus only when needed
- Write a CLAUDE.md (under 200 lines)
- Use Plan Mode before building anything complex
- Run /compact every 15 minutes during long sessions
- Create a .claudeignore for every project
- Disconnect idle MCP servers weekly
Six free configuration habits that address the biggest sources of Claude Code token waste.
Steal forAny tutorial or onboarding doc about Claude Code for non-developers
04:27concept
80/20 Workflow
80% of session time spent in Plan Mode reviewing the proposed approach; 20% in execution. Claimed to cut total token cost on complex tasks by 50-70%.
Steal forAny AI agent workflow that benefits from upfront planning before file mutations
02:50model
Model Tier Decision Rule
- Haiku: rename files, fix typos, write boilerplate
- Sonnet: write functions, refactor, add features
- Opus: complex architecture, multi-file reasoning, hard bugs
Simple task-to-model matching that prevents the most expensive mistake: defaulting Opus for everything.
Steal forClaude Code onboarding checklists, pricing explainers
How they asked for the click.
VERBAL ASK
05:02product
“That's exactly what my free AI cash flow masterclass is all about.”
Two mid-roll blocks (05:02 and 09:07) plus description links. Landing page shown on screen. Offers free 30-day HighLevel trial as the lead magnet. Fairly high-frequency pitch for a 9-minute video.
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
Visual structure at a glance.
