Blog

  • AI Tools: Mods will 10x your Claude Code. Master it in 16 minutes

    Watch on YouTube: https://www.youtube.com/watch?v=MDwCtwPfFGM

    Channel: Nick Puru | AI Automation

    Introduction

    The video from Nick Puru | AI Automation explains how Claude Code mods let you tailor the assistant’s look and behavior using plain‑language prompts, eliminating the need to write code yourself. It demonstrates three practical safety‑and‑visibility mods, shows how to persist them across sessions, and outlines the security considerations that come with giving mods full system access.

    What the video covers

    The presentation begins with a brief overview of what a Claude Code mod is: a small piece of code generated by describing a desired change in natural language. The creator then walks through three example mods that address common workflow concerns:

    • A deletion‑protection safety net that intercepts delete commands and asks for confirmation.
    • A confirmation step before sending messages or emails via connected apps such as Gmail, Slack, or Teams.
    • A receipt panel that surfaces the tools Claude used, web pages searched, and files read after each answer.

    Beyond the demos, the video explains how to save a mod for the current session only or make it load automatically in every new session, how to validate a mod’s capabilities without executing it, and what to do if a mod behaves unexpectedly. The presenter also mentions a free School community where the demonstrated mods and a course on growing an AI agency to $10 k/month are available.

    Step‑by‑step walkthrough of the three示例 mods

    • Deletion‑protection mod – You prompt Claude to watch for any delete operation (e.g., rm, file‑trash commands) and to insert a confirmation dialog before the action proceeds. The mod runs right before the actual deletion, giving you a chance to abort.
    • Confirmation‑before‑sending mod – By describing a rule such as “always ask for confirmation before sending an email, Slack message, or Teams message,” Claude generates a mod that intercepts the send request, shows a prompt, and only forwards the message after you approve.
    • Receipt mod – You ask Claude to create a panel that appears after each answer, listing the web pages consulted, files read, and tool calls made. This receipt helps you audit what Claude accessed and provides transparency for compliance or debugging.

    Each mod is created by typing a plain‑language request into Claude Code, letting the assistant generate the underlying code, and then testing the behavior in either the terminal or the Claude Code desktop tab.

    Tools, numbers and validation

    The video cites several figures to contextualize the Claude Code ecosystem:

    • The launch post for Claude Code garnered 800 k views initially and later reached 4 M views.
    • Claude Code was released on October 1.
    • An audit of 4 000 skills found that over a third had security issues.
    • The agency‑growth course promoted in the video targets $10 k per month.
    • The target year for widespread AI adoption mentioned is 2026.

    Key tools and commands highlighted:

    • Claude plugin validate – runs a safety check that lists what a mod can trigger (file reads, program execution, network access) without actually executing it.
    • Built‑in mods such as the diff view and the “You Should Know” parallel agent are mentioned as examples of what mods can add.
    • Safe mode and hot reboot are presented as ways to disable mods temporarily or enable a mod for the current session only.
    • The video notes that mods are not sandboxed; they run with full access rights, meaning they can read files, run programs, and access the internet.

    Caveats and hype check

    Because mods operate with unrestricted privileges, the presenter stresses the importance of validating any third‑party mod before enabling it. A quote from the video captures this risk:

    Mods are not sandboxed, so there are no restrictions or barriers around them.

    The video also cautions against downloading mods from unknown sources, recommending instead that users ask Claude to write custom mods tailored to their own workflow.

    The promotional segment for the free School community and the agency‑growth course includes a revenue claim of $10 k per month. The notes label this as a hype check: the claim is marketing material and has not been independently verified.

    Concrete next actions

    To apply what you’ve learned, consider the following steps:

    • Update Claude Code to the latest version to ensure mod compatibility.
    • Create a deletion‑protection mod by prompting Claude to intercept delete commands and request confirmation.
    • Test a confirmation‑before‑sending mod for email, Slack, or Teams using the same prompt pattern.
    • Build a receipt mod that shows web pages searched, files read, and tool calls after each answer.
    • Ask Claude to save any useful mod so it loads automatically in every new session.
    • Run Claude plugin validate on any mod you download from the internet to inspect its capabilities before enabling it.
    • Join the free School community via the link in the video description to access the demonstrated mods and the agency‑growth course.
    • If you prefer not to use third‑party mods, continue writing your own mods with Claude to keep full control over security and functionality.
    • For those interested in scaling an AI agency, schedule a quick call with the Reprise team mentioned in the video.
  • Grok Bot: I Gave GrokBot Claude Code, Codex, and Grok Build

    Watch on YouTube: https://www.youtube.com/watch?v=8dxzMgr2tow

    Channel: Kacper Rutkiewicz | AI Made Simple

    Introduction

    The video demonstrates how to run external command‑line interfaces—Claude Code, Codex, and Grok Build—inside a GrokBot instance. It shows that GrokBot works as a relay, forwarding prompts to the CLIs while drawing on the user’s own API subscriptions, and it walks through a live build of a simple one‑page website for a fictional cleaning company.

    What the video covers

    The presenter explains the installation process for each CLI, how to authenticate them with personal Claude, OpenAI, and xAI accounts, and why explicit commands such as “use Claude Code” are required to avoid GrokBot attempting the task itself and consuming its weekly limit. A practical example is built step by step: a cleaning‑company landing page is created, validated with Codex, and enhanced with a price calculator using Grok Build. The video also shows how to clone a personal GitHub repository via GrokBot for remote access and how to set up a webhook that lets Claude Code delegate research tasks to GrokBot, returning results as HTML.

    Step‑by‑step walkthrough

    • Install the Claude Code, Codex, and Grok Build CLIs on the GrokBot environment following the login prompts shown in the video.
    • Authenticate each CLI with the corresponding personal subscription (Claude for Claude Code, OpenAI for Codex, xAI for Grok Build) so the tools use your own API limits.
    • When prompting GrokBot, prepend the request with the explicit tool name—for example, “use Claude Code: create a landing page for a cleaning company”—to ensure the CLI, not GrokBot, performs the work.
    • Use Claude Code to generate the initial HTML and CSS for a one‑page site that includes a header, service list, booking form, and contact section.
    • Run Codex on the generated code to identify and fix three booking‑related issues, such as missing form action attributes and validation gaps.
    • Employ Grok Build to add a functional price calculator that instantly quotes services based on vehicle size (e.g., SUV) and selected extras like pet hair removal.
    • Clone your own GitHub repository (the “Deep Rooted AI OS” example) through GrokBot, enabling you to pull code and run commands from a mobile device.
    • Configure a webhook URL in GrokBot so that Claude Code can send research prompts to it; GrokBot processes the request and returns the result as HTML snippets.
    • Monitor the usage dashboards for Claude, OpenAI, and xAI separately; observe that GrokBot’s weekly consumption remains low because most token usage is offloaded to the external CLIs.
    • Join the presenter’s free “AI Made Simple” community to access a detailed step‑by‑step guide and ask follow‑up questions.

    Tools and numbers mentioned

    • Subscription costs referenced: $200 per month for certain plans, $209 for another option.
    • Plan names: Ultra plan, Super Grok plan, Cursor Pro Plus, Cursor Ultra.
    • Usage percentages: 43% and 44% (illustrating GrokBot’s minimal change when CLIs are used).
    • Time estimates: 8‑10 minutes to complete the demo build.
    • Design detail: 44‑pixel spacing mentioned in the layout.
    • Specific features: free quote request form, SUV vehicle option, pet hair removal add‑on.
    • Model/reference: Opus 5.5 (cited in the context of the demo).
    • Low‑usage figure: 1% (indicating GrokBot’s own consumption when external CLIs handle the workload).

    Caveats and hype check

    The video emphasizes that GrokBot’s weekly usage barely changes when the external CLIs are employed, suggesting a potential reduction in GrokBot‑specific consumption. However, the actual savings depend on individual usage patterns, the specific plans you hold, and how frequently you invoke each tool. The presenter’s claim that “you only need one subscription to get started” refers to the ability to authenticate each CLI with the service you already pay for, but you still need separate accounts for Claude, OpenAI, and xAI to use their respective CLIs. The video also promotes the creator’s free community and guide; viewers should evaluate whether those resources match their learning preferences.

    Concrete next actions

    • Follow the installation steps shown in the video to add Claude Code, Codex, and Grok Build to your GrokBot instance.
    • Log in to each CLI with your personal Claude, OpenAI, and xAI credentials so the tools draw on your own API limits.
    • Always prefix GrokBot prompts with the explicit tool name (e.g., “use Codex:”) to prevent GrokBot from attempting the task and using its weekly quota.
    • Build a simple one‑page site for a service business, then run Codex to catch and fix any form‑handling bugs.
    • Enhance the site with Grok Build by adding a calculator that quotes prices based on vehicle size and optional extras.
    • Clone a personal GitHub repository via GrokBot to enable remote code access from a phone or tablet.
    • Set up a webhook in GrokBot that allows Claude Code to send research tasks and receive HTML‑formatted results.
    • Track your Claude, OpenAI, and xAI usage separately in their respective dashboards to confirm that GrokBot’s own consumption stays low.
    • Sign up for the free “AI Made Simple” community to obtain the detailed walkthrough guide and ask questions about the setup.
  • Grok Bot: Meta Just Dropped Muse Wonder (Better Than Opus 5.5?)

    Watch on YouTube: https://www.youtube.com/watch?v=d_UgqLKUZHY

    Channel: Brock Mesarich | AI for Non Techies

    Introduction

    Meta’s latest announcement, Muse Wonder, has sparked interest among professionals looking for a powerful AI agent that can handle memory‑intensive workflows. Positioned as a direct challenger to Claude Opus 5.5 and the upcoming GPT‑6 Astra, Wonder brings two new capabilities—active memory and active focus—while matching Opus 5.5’s pricing. The following breakdown walks through what the video covers, how you could test the model today, the key numbers presented, where caution is warranted, and concrete steps you can take next.

    What the Video Covers

    The presentation begins with a brief history: Meta claims it rebuilt its AI foundation from scratch roughly 14 months ago, leading to the creation of Muse Wonder as its flagship model. The host explains that Wonder is designed for personal and professional agent tasks, emphasizing its ability to retain context across conversations and to stay focused on complex problems. Internal benchmark results are shared, comparing Wonder to Opus 5.5 on legal reasoning, business process completion, large‑scale programming, and program‑creation tests. Pricing details, access restrictions, and error rates for personal‑data handling are also highlighted. Finally, the video speculates on potential integration with Grok Bot and outlines a timeline for broader availability in the Muse app.

    Step‑by‑Step Walkthrough

    If you already subscribe to Meta’s Muse Code service, you can experiment with Wonder right now through the API. The process looks like this:

    • Log into your Muse Code account and verify that you are on either the $50/month or $200/month tier; these are the only plans that grant API access to Wonder.
    • Generate an API key from the Muse Code dashboard under the “API Access” section.
    • Set the model parameter to “muse-wonder” when calling the Meta API endpoint.
    • Remember the pricing: $4 per million inbound tokens and $20 per million outbound tokens, identical to Opus 5.5’s rates.
    • Begin with a simple prompt to test active memory—ask the model to recall a detail you mentioned three turns earlier.
    • Proceed to a more complex task that requires sustained focus, such as drafting a multi‑section business proposal while asking the model to clarify ambiguous points before proceeding.
    • Monitor token usage to estimate costs; a 1‑million‑token context window allows you to feed large documents or codebases in a single request.

    If you do not yet have a Muse Code subscription, the video advises waiting for the model’s rollout into the free Muse app, which Meta says will happen for paid subscribers at an unspecified future date.

    Tools & Numbers

    The video supplies a set of quantitative claims that help gauge Wonder’s potential:

    • Context window: 1 million tokens.
    • Pricing via Meta API: $4 / million inbound tokens, $20 / million outbound tokens (matching Opus 5.5).
    • Legal task benchmark: Wonder 13.1 % vs Opus 5.5 4.2 % (≈3× improvement).
    • Business process completion: Wonder 45.4 % (no Opus 5.5 figure given, but presented as outperforming).
    • Large‑scale programming: Wonder 57.5 % vs Opus 5.5 46.3 %.
    • Program creation from scratch: Wonder 59 % vs Opus 5.5 70.5 % (Wonder lags here).
    • General intelligence index: Wonder 56 vs Opus 58.
    • Active memory test: Wonder 85.6 % vs Opus ≈81 %.
    • Personal‑data error rate: Wonder 3.4 % (≈1 error per 30 attempts) vs Astra 4.6 %.
    • Muse Code subscription tiers: $50/month and $200/month (API access only).

    A notable quote from the presenter is:

    “active memory that retains user context across dialogues and ‘active focus’ that persists on difficult tasks and seeks clarification.”

    Another excerpt warns:

    “3.4%—that’s still about once every 30 attempts during the test.”

    Caveats & Hype Check

    The host stresses that all performance figures come from Meta’s internal benchmarks; independent validation has not yet been published. Because Wonder is not broadly available via a public API or the free Muse app, real‑world testing remains limited. The pricing advantage is meaningful only if you can access the model, which currently requires a Muse Code subscription. The video’s suggestion that Wonder could soon replace Grok Bot for memory‑heavy workflows is presented as speculative—no official integration roadmap was disclosed. Therefore, treat the superiority claims as preliminary until third‑party evaluations appear.

    Concrete Next Actions

    Based on the information provided, consider the following steps:

    • If you already have a Muse Code account, upgrade to the $50 or $200 tier to obtain API access and run a few test prompts focused on memory retention and task focus.
    • Document token consumption and cost for a representative workload (e.g., analyzing a 200‑page contract) to compare against your current agent’s expenses.
    • When connecting any AI agent to email, calendar, or private documents, factor in the 3.4% personal‑data error rate and implement additional safeguards such as manual review or sandboxed environments.
    • Compare Wonder’s active memory and active focus features against the capabilities of your existing agent (Grok Bot, ChatGPT, etc.) to see whether they address specific pain points in your workflow.
    • Stay tuned for Meta’s announcement of Wonder’s release in the Muse app; once available, reassess whether migrating from a third‑party agent makes sense for your use case.
    • Engage with the creator’s community by commenting on the video with your current AI stack and any early results you observe from testing Wonder.
  • AI Tools: I Fully Automated Google Flow Using Claude Code (Full Walkthrough)

    Watch on YouTube: https://www.youtube.com/watch?v=JEla_mdlfxs

    Channel: Guney Topcu | AI Made Easy

    Overview

    The video demonstrates a fully automated workflow for generating Google Flow videos at no monetary cost by combining the open‑source Flow Studio tool, Claude Code, and the Model Context Protocol (MCP). It shows how creators can stay within Google Flow’s free daily allowance of 50 credits while producing narrated short films using only free APIs and local FFmpeg processing.

    What the Video Covers

    The presenter walks through the entire end‑to‑end process:

    • Installing and configuring Flow Studio via Claude Code.
    • Leveraging Google Flow’s 50‑credit free tier (15 credits per 10‑second video shot, zero credits for still images and character creation).
    • Obtaining AI voiceovers at zero cost by routing Flow Studio to Google AI Studio’s free Text‑to‑Speech API instead of Flow’s native TTS (which costs 7 credits per clip).
    • Assembling the final video locally with FFmpeg, incurring no credit usage.
    • Following the five‑step pipeline: CAST → FRAMES → SHOTS → VOICE → CUT.
    • Using Exact Join for background continuity and Character Lock for location jumps.
    • Accessing a local dashboard at 127.0.0.1 with seven tabs, each corresponding to a workflow stage, or issuing plain‑English commands through Claude Code.

    Step‑by‑Step Walkthrough

    1. Setup
      • Install Node.js v22+ if not already present.
      • Ensure Google Chrome and FFmpeg are available (the installer can add FFmpeg automatically).
      • Run the Flow Studio installation command from the GitHub repo (github.com/GTAI-1/flow-mcp).
      • During setup, a dedicated Chrome profile opens; log in to Google Flow.
      • Create a free API key in Google AI Studio (aistudio.google.com) and paste it into the VOICE tab of Flow Studio.
    2. Verify Connection
      • Ask Claude Code: “Check Flow and tell me my credit balance.” The response should show the current free‑credit count (starting at 50 per day).
    3. CAST – Character Creation
      • In the CAST tab (or via Claude), describe the desired character in plain English.
      • Character creation and edits cost zero credits, allowing unlimited iterations.
    4. FRAMES – Keyframe Stills
      • Generate still images that will serve as keyframes for each shot.
      • Stills are produced with the Nano Banana 2 model and incur zero credits.
      • Review the outputs; request adjustments until the visual composition matches the vision.
    5. SHOTS – Video Clips
      • Convert each approved keyframe into a 10‑second video shot.
      • Each shot consumes 15 credits (Omni 1.1 Flash model).
      • Choose Exact Join when consecutive shots share the same background to maintain continuity; use Character Lock when the scene changes location.
      • Enable the credit safety guard (e.g., set a personal limit of 25 credits) to prevent accidental overruns; the system will block a shot that exceeds the limit and display a message like “OVER YOUR LIMIT: Not generated. 60 > 25 credits.”
    6. VOICE – Narration
      • In the VOICE tab, input the script for narration.
      • Route the request to Google AI Studio’s free TTS API, resulting in zero credit usage.
      • If the native Flow TTS were used, each clip would cost 7 credits.
    7. CUT – Final Assembly
      • Download the generated video clips and audio files.
      • Use FFmpeg locally to concatenate clips, overlay the voiceover, and add any desired transitions or effects.
      • This step incurs no Google Flow credits.
      • Export the final video in the desired format.

    Tools, Numbers, and Limits

    • Google Flow free tier: 50 credits per day.
    • Cost per 10‑second video shot: 15 credits.
    • Still images and character creation/edit: 0 credits.
    • Native Flow TTS voiceover: 7 credits per clip.
    • Voiceover via Google AI Studio API: 0 credits.
    • Restyle edit (modifying an existing clip): 40 credits – significantly higher than generating a new 10‑second clip.
    • Flow Studio provides 39 presets (30 camera moves, 9 visual effects).
    • Required prerequisites: Node.js v22+, Google Chrome, FFmpeg, a Google Flow login, and a free Google AI Studio API key.
    • Local dashboard accessible at 127.0.0.1 with seven tabs matching the workflow stages.

    Caveats and Hype Check

    “I made both of these clips for free without sitting inside Google Flow writing prompt after prompt.”

    The workflow is cost‑free only as long as the user remains within Google Flow’s daily 50‑credit allowance. Heavy usage — particularly frequent restyle edits at 40 credits each — can quickly exhaust the free tier, after which additional credits would need to be purchased or the user would need to wait for the next day’s allocation. The video does not make unverified revenue claims; it simply contrasts the zero‑cost approach with typical commercial Chrome extensions that charge around $30 per month.

    Concrete Next Actions

    • Install Node.js v22+ if not already installed.
    • Run the Flow Studio setup command from the GitHub repository.
    • Confirm that Chrome and FFmpeg are available (the installer can add FFmpeg).
    • Log in to Google Flow via the Chrome profile launched during setup.
    • Obtain a free API key from Google AI Studio and paste it into Flow Studio’s VOICE tab.
    • Test the connection by asking Claude Code to report your current credit balance.
    • Begin character creation in the CAST tab using natural‑language descriptions.
    • Generate and refine keyframe stills in the FRAMES tab.
    • Produce video shots in the SHOTS tab, selecting Exact Join or Character Lock as appropriate.
    • Create the voiceover in the VOICE tab, ensuring the Google AI Studio API key is active.
    • Assemble the final video locally with FFmpeg in the CUT tab.
  • AI Tools: Anthropic’s Engineers Stopped Building AI Agents. Here’s What They Build Instead.

    Watch on YouTube: https://www.youtube.com/watch?v=VxGIopUQVKo

    Channel: Sharbel A.

    Introduction

    The video from Sharbel A. explains why Anthropic’s engineers shifted from building a separate AI agent for every task to creating reusable “skills.” A skill is a lightweight, self‑contained unit that can be installed once and used repeatedly, much like an app on a smartphone. This approach reduces the overhead of maintaining many half‑trained agents and lets a single agent gain many capabilities through a library of skills.

    What the video covers

    The presentation walks through the concept of a skill, shows how to create one using three different methods, and explains how to share or discover existing skills in community marketplaces. It also highlights the mechanics of progressive disclosure, the structure of the skill.md file, and practical safety tips for installing third‑party skills.

    Step‑by‑step walkthrough of creating a skill

    • Define the task – Identify a repetitive job you want your AI agent to perform (e.g., searching a niche on VidIQ, formatting a report, or launching a specific workflow).
    • Create the skill folder – Make a new directory on your local machine; inside it place a file named skill.md.
    • Write the skill metadata – At the top of skill.md add a name and a description. The description tells the agent when the skill should be activated (think of it as a trigger phrase or condition).
    • Add step‑by‑step instructions – Below the metadata, list the exact actions the agent must take to complete the task. Use clear, imperative language so the agent can follow each step without ambiguity.
    • Save and test – Save the file, then point your agent at the folder. The agent will first read only the name and description; if those match the current context, it will load the full skill and execute the instructions.
    • Refine – Run the skill a few times, observe any mismatches, and adjust the description or instructions until the agent reliably triggers and completes the task.

    Three creation methods demonstrated

    • Manual authoring – You write the skill.md file yourself, following the structure above.
    • Claude‑guided generation – In the Claude UI, use the “create with Claude” option: describe the job in natural language, let Claude draft a skill, then edit the generated skill.md for accuracy.
    • Screen recording – Record yourself performing the task, upload the recording to Claude, and ask it to learn the steps. Claude will produce a skill that mirrors the recorded workflow.

    Tools and numbers mentioned

    • Claude – the underlying AI model used to create and run skills.
    • VidIQ – example tool referenced in a prompt (“YouTube pockets”).
    • Hermes, Codex, Cursor, Permees – additional tools cited as examples of what skills might interact with.
    • Cloud (marketplace), Skills MP, Lobe Hub, GitHub – platforms where existing skills can be found or shared.
    • Find Skills skill – a helper skill for discovering other skills.
    • Agent Hermes’ Mission Control – an example of a skill that orchestrates multiple actions.
    • skill.md – the core file that defines a skill.
    • Plus sign (UI element) – the button used to add a new skill in the Claude interface.

    Caveats and hype check

    The video frames the skill concept as a productivity improvement, not as a revenue‑generating scheme. It avoids making explicit earnings promises, affiliate promotions, or unverified claims. The tone remains educational and tool‑focused. A practical warning is included: always read the entire skill description and scan it for potentially malicious content before installing any third‑party skill.

    Concrete next actions

    • Identify a repetitive task you currently perform with your AI agent and draft a skill.md file for it (include name, description, and step‑by‑step instructions).
    • Try creating a skill manually using the Claude UI to become familiar with the folder and file structure.
    • Use Claude’s “create with Claude” feature: describe the job, let Claude generate a draft skill, then refine the skill.md file.
    • Record a screen walkthrough of a task, have Claude learn from the recording, and export the resulting skill for reuse.
    • Search the Claude skills explorer, GitHub, Skills MP, or Lobe Hub for existing skills that match your needs, then import them into your agent.
    • Before installing any third‑party skill, review its description and instructions for signs of unwanted or harmful behavior.
    • Share your own skill by exporting the folder containing skill.md and distributing the file or a download link to teammates or the community.
  • Trading: The UNTHINKABLE is About to Happen to Stocks (but most will invest wrong)

    Watch on YouTube: https://www.youtube.com/watch?v=6pm5KqQw6RI

    Channel: Tom Nash

    Introduction

    The video from Tom Nash argues that most investors lose money not because they lack information, but because they lack a repeatable system that turns data into disciplined action. By treating stocks as underlying businesses and applying a set of predefined rules, the presenter claims investors can remove guesswork, stay invested through volatility, and achieve long‑term compounding.

    What the Video Covers

    Tom Nash outlines a three‑part framework:

    • A mindset shift: focus on earnings, fundamentals, and business quality rather than price noise or media opinion.
    • Practical rules for entering, adding to, and trimming positions (trim rules, double‑down DCA).
    • A quantitative quality screen (the 125‑point test) used to evaluate whether a stock meets the criteria for a long‑term hold.

    He also shares historical examples, personal portfolio results, and invites viewers to a free live masterclass where the full methodology and two undisclosed stock picks will be revealed.

    Core Framework Explained

    Trim Rules

    Instead of letting winners run indefinitely, the presenter suggests taking partial profits at predefined price levels and recycling that cash into a dollar‑cost‑averaging (DCA) pool. The example given is:

    • Sell 10 % of a position when it is up +50 % from the purchase price.
    • Sell an additional 20 % when the position is up +100 %.
    • The proceeds from these sales are directed to a DCA fund that can be deployed when market conditions meet the double‑down criteria.

    Double‑Down DCA

    The approach adjusts the size of regular purchases based on recent price action relative to a yearly high:

    • If a broad index (e.g., S&P 500) is down ≥10 % from its yearly high, double the monthly DCA amount.
    • If an individual stock is down ≥20 % from its yearly high, double the monthly DCA amount for that stock.
    • If a stock rises >20 % within a 30‑day window, reduce the DCA amount to half‑speed (i.e., buy half the usual monthly amount).

    These rules are intended to increase exposure during pullbacks while tempering buying during rapid rallies, thereby averaging into positions without trying to pick exact tops or bottoms.

    125‑Point Quality Test

    The presenter describes a checklist that scores a stock across multiple dimensions. A higher score indicates a stronger fundamental profile and, in his view, a higher likelihood of delivering long‑term price appreciation. The components mentioned include:

    • Cash versus debt levels
    • Revenue growth trends
    • Operating margin
    • Short interest
    • Institutional ownership
    • Scalability of the business model
    • Five‑year track record of beating the S&P 500
    • Presence of a durable moat
    • CEO quality and track record
    • Recession‑proof characteristics
    • Alignment with secular trends
    • Mission‑centric culture
    • Talent depth and elite employee base

    Each factor contributes points toward a total of 125; the presenter uses this score to decide whether to hold, add to, or trim a position.

    Historical Examples and Performance Numbers

    To illustrate the power of staying the course, the video walks through price trajectories for four stocks:

    • Palunteer: $6 → $7 → $10 → $23 → $18 → $6 → $17 → $75 → $177 → $200 → $137 → $209
    • Nvidia: $20 → $150 → $94 → $230
    • Data Dog: $133 → $105 → $188 → $293
    • Bloom Energy: $156 → $119 → $280

    The associated returns cited are:

    • Palunteer ≈ 2600 %
    • Nvidia ≈ 1500 %
    • Data Dog ≈ 120 %
    • Bloom Energy ≈ 80 %

    The presenter’s personal portfolio, weighted as 40 % Palunteer, 40 % S&P 500, and 20 % Tesla, is said to have returned roughly +565 % versus a +75 % benchmark (S&P 500) over the same period, translating to an approximate +1300 % raw gain before weighting.

    Additionally, a Vanguard study is referenced showing that wealthy portfolios typically hold about 90 % in U.S. stocks, keep cash around 13 %, and exhibit low trading activity (≈ 8 % turnover), underscoring the value of long‑term, low‑turnover investing.

    Tools, Thresholds and Rules Summary

    • Trim rules: sell 10 % at +50 %, sell an additional 20 % at +100 %; recycle proceeds into DCA.
    • Double‑down DCA triggers:
      • Index ↓≥10 % yearly high → 2× monthly buy.
      • Stock ↓≥20 % yearly high → 2× monthly buy.
      • Stock ↑>20 % in 30 days → ½× monthly buy.
    • Quality test: 125‑point scale covering cash/debt, revenue growth, operating margin, short interest, institutional holding, scalability, 5‑yr S&P beat, moat, CEO, recession‑proof, secular trend, mission‑centric culture, talent.

    Caveats and Hype Check

    The video presents impressive personal returns (e.g., a weighted +565 % versus a +75 % benchmark) and claims of 500 %+ outperformance. These results are shown without independent verification or audited documentation, so they should be viewed as illustrative rather than guaranteed outcomes for any investor.

    The promotion of a free masterclass creates a sense of urgency (“Oct 17, 2 p.m. ET”) that may encourage sign‑ups before the viewer has fully evaluated whether the system aligns with their own risk tolerance, investment horizon, and financial situation.

    As with any strategy, past performance does not guarantee future results, and the effectiveness of the trim rules, double‑down DCA, and quality test will depend on market conditions, individual stock selection, and disciplined execution.

    Concrete Next Actions

    If you wish to experiment with the framework presented, consider the following steps:

    • Reserve a spot for the free masterclass on October 17 at 2 p.m. ET via the video description or pinned comment.
    • Create a one‑page checklist for each stock you are evaluating, assigning points for each of the 125‑quality factors mentioned.
    • Determine a baseline monthly DCA amount that fits your budget and set up automatic transfers to a dedicated investment account.
    • Define your personal trim rules (e.g., take 10 % profit at +50 %, 20 % at +100 %) and decide how you will recycle the proceeds into your DCA pool.
    • Implement the double‑down logic: monitor your chosen index and each holding’s yearly high; increase purchases when the thresholds are met and reduce to half‑speed when a stock spikes >20 % in 30 days.
    • Avoid making buy or sell decisions based solely on news headlines or social media chatter; rely on your pre‑defined rules and quality scores.
    • Track your portfolio’s performance against a benchmark such as the S&P 500 on a quarterly basis to assess whether the process is adding value.
    • Review each holding’s quality score every quarter; use the results to decide whether to hold, add, or trim the position.
    • Maintain a simple journal of emotions and decisions to detect moments when you deviate from the system and to reinforce disciplined behavior.
    • After the masterclass, integrate the two undisclosed stock picks into your watchlist and apply the same quality‑scoring and DCA framework before allocating capital.
  • AI Tools: this is boring but you’ll outwork everyone

    Watch on YouTube: https://www.youtube.com/watch?v=E8Oagqi5CBM

    Channel: Daniel Barada

    Introduction

    The video titled “this is boring but you’ll outwork everyone” from Daniel Barada’s channel introduces a practical framework for measuring and improving personal performance. Rather than treating skill as a single static level, the presenter explains Jared Tendler’s “inchworm theory,” which visualizes ability as a range between a peak (A‑game) and a trough (C‑game). The core idea is that genuine progress occurs when both ends of that range shift forward together, making the average performance higher and more stable.

    What the Video Covers

    The presentation breaks down the inchworm model into several digestible concepts:

    • Performance is a fluctuating range, not a fixed point.
    • Most daily activity lives in the middle of that range; variation is normal and driven by factors like stress, sleep, and emotion.
    • Expanding the front means pushing the A‑game higher through deliberate practice, learning, and taking on slightly harder challenges.
    • Raising the back involves reducing the frequency, intensity, or recovery time of the C‑game—those worst‑case behaviors that cost time, money, or emotional energy.
    • Real improvement is visible when the old C‑game starts producing outcomes that the former self would have respected.
    • When both ends move forward, the range compresses, raising the average and lowering volatility.
    • Development cycles consist of picking one front‑end target and one back‑end weakness, working on both, then reassessing the range.
    • Effective tracking relies on observable behaviors rather than vague traits like “disciplined” or “confident.”
    • Early warning signs and pre‑planned minimum responses help intercept C‑game patterns before they escalate.
    • A new cycle begins when former A‑game behaviors appear in ordinary performance and former C‑game behaviors fade.

    Step‑by‑Step Walkthrough

    To apply the inchworm theory, the video suggests a concrete process:

    1. Select a life domain (health, work, relationships, inner life).
    2. Identify your current A‑game and C‑game using specific, observable behaviors from the past month.
    3. Choose a front‑end target: a new capability just beyond your normal that you can practice repeatedly.
    4. Choose a back‑end target: the recurring C‑game behavior that costs you the most time, money, or emotional energy.
    5. Define an early warning signal for the back‑end target and a simple minimum response to deploy when that signal appears.
    6. Track both targets over several weeks, noting frequency, intensity, and recovery time for each.
    7. When the old A‑game shows up as routine behavior and the old C‑game diminishes, remap the range and start the next cycle.

    This loop creates a measurable feedback system: you see whether the floor is rising, the ceiling is lifting, and whether the distribution as a whole is shifting forward.

    Tools & Numbers

    The video does not name any specific software, apps, or quantitative tools beyond referencing the YouTube source itself. No financial figures, performance metrics, or paid products are cited. The emphasis is on observable behavior tracking, which can be done with a simple journal, spreadsheet, or habit‑tracking method of your choice.

    Caveats & Hype Check

    The presenter avoids exaggerated revenue promises or sensational claims. The call‑to‑action is modest: a free community, a newsletter, and optional one‑on‑one coaching sessions are mentioned, but there is no pressure to purchase anything. This keeps the focus on the conceptual framework rather than on selling a product.

    “The video does not make exaggerated revenue promises or push paid products; it promotes a free community, newsletter, and optional one‑on‑one calls, which is a modest call‑to‑action without hype.”

    Because the model relies on self‑observation, its effectiveness depends on honest tracking and consistent application. If the chosen behaviors are too vague or the tracking is inconsistent, the perceived shift in range may be illusory.

    Concrete Next Actions

    To begin using the inchworm approach right away, consider the following steps:

    • Pick one area of life you want to improve (e.g., workout routine, project delivery, communication with a partner).
    • Write down your current A‑game and C‑game for that area, using concrete actions you have actually performed in the last four weeks (e.g., “ran 5 km in under 25 minutes” for A‑game; “skipped workout and ate fast food three times” for C‑game).
    • Select a front‑end target that is just beyond your usual performance but achievable with repeated practice (e.g., “add interval sprints to twice‑weekly runs”).
    • Select a back‑end target that represents a costly pattern you want to reduce (e.g., “checking phone during work blocks leading to 20‑minute loss of focus”).
    • Identify an early warning sign for the back‑end target (e.g., “feeling the urge to check notifications after 10 minutes of focused work”) and define a minimum response (e.g., “close the browser tab and take three deep breaths”).
    • Set up a simple tracking method—a notebook, a Google Sheet, or a habit‑app—to log each occurrence of the front‑end practice and each back‑end event, noting intensity and recovery time.
    • Review the logs every two weeks. When the former A‑game appears as regular behavior and the former C‑game noticeably declines, redraw your A‑game/C‑game range and start the next cycle.

    Following this process gives you a tangible way to see whether you are truly expanding your capabilities while also strengthening your baseline—turning the abstract idea of “getting better” into a measurable, repeatable routine.

  • AI Tools: 10 New Github Repos to Make Money in 19 mins

    Watch on YouTube: https://www.youtube.com/watch?v=zwQmodmp1To

    Channel: Jack Roberts

    Introduction

    Jack Roberts presents a rapid survey of ten newly popular GitHub repositories that enable AI agents to perform creative, browsing, reverse‑engineering, workflow orchestration, and security‑audit tasks. The video frames these open‑source projects as alternatives to costly SaaS subscriptions and as building blocks for agent‑driven productivity that could help users reduce expenses and increase output.

    What the video covers

    The presentation walks through each repository, highlighting its core functionality, recent traction metrics (stars, views, installations), and a brief demonstration of how an AI agent might interact with the tool. Roberts also ties the tools to his own Claude Code masterclass and Agentic OS setup, suggesting that combining these repos with his training could unlock money‑making opportunities.

    Step‑by‑step walkthrough of the ten repositories

    • OpenCraft Suite – A collection of AI‑controllable creative apps (PhotoCraft, FilmCraft, VectorCraft, etc.) that aims to replicate Adobe Creative Cloud. The suite garnered 39 k+ GitHub stars in ten days and 1.6 million announcement views.
    • Compositor – A 12 MB macOS‑native image editor designed for lightweight AI‑controllable editing. It has attracted ~2.3 million views and roughly 1.7 k stars.
    • Ego Lite – An isolated browser sandbox for AI agents accessible at lite.ego.app, preventing cursor hijacking and preserving user sessions. The project holds 17 k GitHub stars.
    • REA (Letter Run) – A reverse‑engineering tool that extracts UI, logic, and data layers from applications. It rose to 60 k stars in seven days (65 k total) and generated 772 k views on X.
    • 21st.dev MCP integration – Provides production‑ready UI components via the Model Context Protocol, used to build Glaido’s onboarding interface.
    • Skills.sh (Vercel Labs) – A meta‑skill repository that enables agents to discover and install tools, logging over 3.3 million installations.
    • Orca – An orchestrator for parallel agent swarms, holding 89 k stars with about 75 % gained in the last 30 days, and offering a mobile companion app.
    • Zapier MCP Server – Grants agents granular access to thousands of SaaS APIs (Google Workspace, Slack, Notion, etc.) with permission toggles.
    • The Arena Skill – Runs a tournament of 100 Claude instances to identify the best solution, accumulating 4.3 million social‑reel views and 406 GitHub stars.
    • Universal Modder – Automates game modding by reverse‑engineering local game assets and generating playable mods.
    • Cloudflare security‑audit skill – Performs a six‑phase autonomous vulnerability assessment, earning 27 k stars since mid‑September.
    • SlopMonster – Strips AI‑generated “slop” from prose, converting vague copy into concrete, rhythmic marketing language.

    Key tools and metrics

    • OpenCraft Suite: 39 k+ stars (10 days), 1.6 M views.
    • Compositor: 12 MB binary, 2.3 M views, ~1.7 k stars.
    • Ego Lite: 17 k stars, sandbox at lite.ego.app.
    • REA (Letter Run): 65 k total stars, 60 k stars in 7 days, 772 k X views.
    • 21st.dev: MCP integration for UI components.
    • Skills.sh: 3.3 M tool installations.
    • Orca: 89 k stars, ~75 % growth in past 30 days.
    • Zapier MCP Server: API access for SaaS platforms.
    • The Arena Skill: 4.3 M social views, 406 stars.
    • Universal Modder: Game‑asset reverse engineering.
    • Cloudflare security‑audit skill: 27 k stars.
    • SlopMonster: AI‑copy cleanup tool.

    Caveats and hype check

    While the video showcases rapid growth and impressive star counts, it also acknowledges that the revenue potential remains speculative. Roberts promotes his own Claude Code masterclass and Agentic OS setup, implying significant earnings from these tools, but no concrete earnings proof or detailed business case is presented. Claims of making money should therefore be treated as aspirational rather than guaranteed.

    > “Never allow an AI agent to install third‑party community skills without auditing”

    > “The result replaces vague corporate abstractions with concrete, rhythmic, and factual language.”

    Concrete next actions

    • Install PhotoCraft via Claude Code using the OpenCraft Suite repository link.
    • Try Compositor with Homebrew: brew install compositor.
    • Set up the Ego Lite browser sandbox at lite.ego.app for isolated AI browsing.
    • Add 21st.dev to your Claude Code MCP configuration to fetch UI components.
    • Run skills.sh to discover and install needed agent skills, but first audit any unknown skill with an LLM.
    • Deploy Orca orchestrator via Homebrew: brew install orca to run parallel agent tasks.
    • Configure the Zapier MCP Server to grant agents limited SaaS access (e.g., read‑only Gmail).
    • Run the Cloudflare security‑audit skill before pushing any application to production.
    • Use SlopMonster to clean AI‑generated marketing copy and improve conversion.
  • AI Tools: 喺香港用 Claude 唔使 VPN:雲端電腦 Zo Computer 教學

    Watch on YouTube: https://www.youtube.com/watch?v=jFWBMQfkNgE

    Channel: 阿石OMP

    Overview

    The video from 阿石OMP explains how users in Hong Kong can continue to use Claude Code without triggering Anthropic’s account‑ban mechanisms. The core issue identified is that commercial VPN services often route traffic through IP ranges that Anthropic flags as proxy or VPN endpoints, and they can also leak local system fingerprints. By moving the workload to a US‑based cloud workstation, the user’s local network and device characteristics are isolated from the Claude service, reducing the risk of automated abuse‑prevention triggers.

    The tutorial focuses on Zo Computer, a browser‑based Linux environment hosted in the United States. It shows how to launch Claude Code inside that environment, complete the OAuth login flow without exposing a local VPN, and optionally integrate Claude Max API credits. The creator also discloses a $10 referral incentive for Zo Computer but stresses that the video is intended to help colleagues who have been locked out of their accounts.

    What the video covers

    • Why commercial VPNs lead to Claude account bans (flagged IP ranges, fingerprint leakage).
    • How Zo Computer provides an isolated US‑based Linux workstation accessed through a browser.
    • The process of launching Claude Code directly in Zo Computer’s terminal.
    • The safe OAuth login method: copying the authorization URL and pasting it into Zo Computer’s internal browser, never clicking the “Open” button on the local machine.
    • How to add Claude Max API credits via the “Bring Your Own Key” option.
    • Pricing details for Zo Computer’s Pro and Basic plans, including bundled AI credits.
    • A disclaimer about the creator’s affiliate relationship with Zo Computer.

    Step‑by‑step walkthrough

    • Sign up for Zo Computer at zo.computer and select either the Pro or Basic plan.
    • Once the virtual workstation is ready, open the built‑in browser from the Zo Computer dashboard.
    • Navigate to Settings → AI → Providers and locate the Claude Code entry.
    • Click the “Connect” button next to Claude Code; a modal appears with an OAuth authorization URL.
    • Use the copy icon to copy the URL. Do not click the Open button in the modal.
    • Paste the copied URL into Zo Computer’s internal browser, log in to your Claude account, and copy the verification code presented after authentication.
    • Return to the Connect Claude Code modal in Zo Computer, paste the verification code, and submit to finish linking the account.
    • (Optional) To use Claude Max API credits, go to Settings → AI → Providers → Bring Your Own Key and paste your Claude Max API key.
    • Launch Claude Code from the terminal inside Zo Computer or start a New Chat to begin using Opus, Sonnet, Haiku, or Fable models.

    Pricing and specifications

    • Pro plan: $64 USD per month – 16 CPU cores, 128 GB RAM, 10 active background services, 5 custom domains, $40 USD of bundled AI credits per month.
    • Basic plan: $18 USD per month – lighter resource allocation (exact cores/RAM not specified in the notes), $10 USD of bundled AI credits per month.
    • No permanent free tier is mentioned; both plans are paid subscriptions.
    • The video also references a $200 USD per month figure and $200 USD worth of Anthropic API credits, which appear to be example amounts for high‑usage scenarios rather than Zo Computer pricing.
    • Referral incentive: $10 USD per paying customer referred to Zo Computer (disclosed but no link provided).

    Considerations and limitations

    I strongly advise you NEVER to click this button to open the link directly.

    The video emphasizes that clicking the OAuth “Open” button on a local machine would expose the user’s IP and potentially trigger Anthropic’s abuse‑prevention systems. By keeping the authentication flow inside the Zo Computer browser, the user’s local network remains separate from the Claude service.

    The creator notes that the method is based on personal experience and does not guarantee that accounts will never be banned. Anthropic’s automated systems may evolve, and the effectiveness of isolating the workload could change over time.

    There is no claim of guaranteed revenue or profit from using Claude Code; the tone remains instructional rather than promotional.

    The affiliate disclosure is present, but no referral link is shared, which aligns with a statement that the tutorial aims to assist the community rather than drive marketing revenue.

    Immediate actions

    • Visit zo.computer and create an account.
    • Choose the Pro plan if you need the full 16‑core/128 GB configuration and the $40 USD monthly AI credit bundle, or select the Basic plan for a lower‑cost entry point.
    • After the workstation provisions, open Settings → AI → Providers.
    • Locate Claude Code, click Connect, and copy the OAuth URL (do not use the Open button).
    • Paste that URL into Zo Computer’s built‑in browser, log in to Claude, and copy the verification code.
    • Return to the modal, paste the code, and submit to complete authentication.
    • If you possess a Claude Max API key, add it via Bring Your Own Key under the same Providers menu.
    • Open the terminal inside Zo Computer and run claude-code (or start a New Chat) to begin using the desired models.
  • Marketing & Lead Gen: META lead forms are cooked. Do this instead.

    Watch on YouTube: https://www.youtube.com/watch?v=jn-0nhO5iFg

    Channel: Samuel Darby

    Introduction

    Samuel Darby argues that traditional Meta lead forms lose prospects because of delayed follow‑up. He proposes an AI‑powered booking funnel that lets leads self‑qualify, schedule, and instantly chat via WhatsApp or SMS while their intent is still hot.

    What the video covers

    The video explains why lead decay happens after a static form submission, cites a Harvard Business Review study on response time, outlines a four‑step funnel, shows how to build the frontend with Claude and host it on Vercel, and details the direct integration with GoHighLevel using Private Integration Tokens. Darby also promotes his Local Ads Lab membership and a high‑ticket accelerator cohort.

    Step‑by‑step funnel walkthrough

    1. Low‑friction landing page / micro‑quiz – The first question is a simple binary choice (e.g., “Do you own your home? Yes/No”) to trigger a micro‑commitment before asking for contact info.
    2. Opt‑in form – After the quiz, the visitor submits their contact details.
    3. Native calendar self‑scheduling – The lead picks a time slot directly on the page.
    4. Confirmation with instant chat – On the confirmation screen the lead can add the event to Google Calendar and start a two‑way WhatsApp or SMS conversation that is pre‑populated with context.

    All quiz answers are concatenated into a single custom text field called Survey Answers in GoHighLevel to avoid field proliferation. The frontend code is generated with Claude, deployed to Vercel, and communicates directly with GoHighLevel using the Location ID and a Private Integration Token (Contacts, Calendars, Conversations scopes). This bypasses Zapier/Make, reduces latency, and eliminates automation failure points.

    Tools and numbers mentioned

    • $99 per month – price for Local Ads Lab (early/low price, set to rise)
    • 6 participants per cohort – limit for the High‑Ticket Accelerator
    • 2,241 companies – referenced as part of the Lab’s reach
    • 7× more likely – chance of conversion when responding within 1 hour (Harvard Business Review)
    • 60× more likely – reduction in conversion when delayed 24 hours (Harvard Business Review)
    • 1 hour – ideal response window
    • 24 hours – delayed response window
    • Claude – AI used to generate funnel code
    • Vercel – hosting platform for the frontend
    • GoHighLevel (GHL) – CRM/automation platform
    • Private Integration Token – authentication method for direct API access
    • Location ID – identifier for the GHL sub‑account
    • CloseBot, Appointo, KwikFrames, Skool, app.leadflo.co – mentioned as related tools or platforms
    • WhatsApp Business API, SMS – channels for instant post‑booking chat
    • Google Calendar – option for leads to add the booked event

    Caveats / hype check

    The video cites strong conversion multipliers (7×, 60×) from a Harvard Business Review study. These figures are genuine but presented as guaranteed results for the funnel; actual outcomes depend on execution, offer quality, and audience. The $99/mo price for Local Ads Lab is labeled an “early/low price” with an imminent increase, a common urgency tactic. No explicit revenue promises are made, but the emphasis on rapid results and exclusive coaching may overstate typical outcomes.

    Concrete next actions

    • Audit your current Meta lead forms and replace any dead‑end thank‑you page with a self‑scheduling calendar step.
    • Create a micro‑quiz where the first question is a simple binary choice (e.g., “Do you own your home? Yes/No”).
    • In GoHighLevel, add a single custom text field called Survey Answers and map all quiz responses into it via concatenation.
    • Generate the funnel frontend code by prompting Claude with the desired quiz flow, calendar integration, and confirmation screen.
    • Deploy the code to Vercel, connect it to your GHL sub‑account using the Location ID and a Private Integration Token with Contacts, Calendars, and Conversations scopes.
    • Add a one‑click “Add to Google Calendar” button and a WhatsApp/SMS button that opens a pre‑populated chat on the confirmation page.
    • Test the end‑to‑end flow: quiz → opt‑in → calendar pick → confirmation → instant chat, ensuring data appears in GHL.
    • Consider joining Samuel Darby’s Local Ads Lab ($99/mo) for ready‑made funnel templates and Claude prompts if you prefer a shortcut.
    • If you want hands‑on help, apply for the High‑Ticket Accelerator cohort (limited to 6 spots).