The argument in one line.
Writers can optimize their Claude Code workflows by using /context to visualize token usage, /stats to track writing patterns and model performance, and /plugins to integrate Notion and design tools directly into their content systems.
Read if. Skip if.
- A writer or content creator building a Claude Code system who wants to understand how /context, /stats, and /plugins commands optimize their workflow.
- Someone managing multiple writing agents, knowledge bases, and assets inside Claude Code who needs visibility into token usage and context allocation.
- A creator already using Claude Code for newsletters, lead magnets, or content production who wants to troubleshoot degrading output quality.
- You're using Claude through the web interface or mobile app — this walkthrough is specific to Cursor and Claude Code editor setup.
- You haven't built a Claude Code system yet and don't have agents, knowledge bases, or custom instructions in place — you'll need that foundation first.
The full version, fast.
Three new Claude Code slash commands turn a writing system from a black box into a measurable workspace. The /context command renders a live breakdown of token usage across system prompt, MCP tools, custom agents, memory files, and free space, so you can spot bloat � MCP servers often dominate while agents cost almost nothing � and prune deliberately. The /stats command surfaces a usage dashboard covering sessions, streaks, peak hours, and model mix, giving writers real visibility into their own habits. The /plugins command opens an official directory of installable integrations, including Notion for two-way document sync and a front-end design plugin that escapes generic AI aesthetics. Together they let you audit, measure, and extend a content workflow without guessing what Claude is doing under the hood.
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.

01 · Intro -- writer-first framing
Alex positions against developer-focused Claude Code content. States the three commands up front. Shows Cursor setup with Claude Code Cheat Sheet visible on the right.

02 · /context -- what is eating your window
Live demo of /context token-level breakdown. Key surprise: two MCPs (Airtable + Notion) consume 21.6% of context. Custom agents take only 0.1%. Full file tree of writing system revealed.

03 · /context -- MCP deep-dive and agent roster
Actual MCP token costs shown (Notion tool-by-tool on screen). Six agents: content repurposing, social media writer, newsletter writer, researcher, community engagement, marketing writer. Plans to scale to 15-20 agents.

04 · /stats -- usage dashboard
325 sessions, Opus 4.5 dominant, current streak, active days, peak hours. Validates $200/month Max plan for all-day use without rate limits.

05 · /plugins -- Discover page and Notion integration
Official Anthropic plugins gallery (40 plugins). Highlights Notion workspace integration. The on-screen cheat sheet was built live using the Notion MCP. Project-level install scoping recommended.

06 · frontend-design plugin and CTA
Brief demo of frontend-design plugin for production-grade HTML. Dual CTA: Substack paid tier for cheat sheet and starting folder, plus master classes.
Lines worth screenshotting.
- The /context slash command gives writers a visual breakdown of what is consuming their context window — system prompt, MCPs, agents, and messages — without requiring developer knowledge.
- MCP tools can consume over 20% of the context window — often more than the system prompt itself — which is a surprising finding for non-developers who added MCPs for convenience.
- The /stats command shows session count, active days, peak usage hours, model breakdown, and streak length — giving writers insight into their own Claude Code usage patterns.
- The /plugins command opens a discovery page for 40+ official Anthropic plugins, including Notion and Asana, installable directly from inside Claude Code.
- The Notion plugin connects Claude Code to your Notion workspace so agents can read, search, and update pages without manual copy-paste between tools.
- Claude Code is not only for developers — content repurposing, newsletter writing, social media drafting, and research can all run as named agents inside a writing system.
- Context profiles (JSON files describing your voice, business, and ideal client) are a low-token way to give Claude Code stable context without burning space on long system prompts.
- Agent files inside .claude take up only 0.1% of context — you can have six or more specialized writing agents without meaningful context cost.
- The Opus 4.5 Max plan ($200/month) gives writers unlimited daily usage with their best model — working all day inside Claude Code without hitting rate limits.
- Knowing which MCP is consuming the most context lets you make an informed decision about which connections to keep active and which to disable for a given session.
- A writing system inside Claude Code with agents, knowledge base, newsletters, and visual assets is a real production workflow, not a developer's side project.
- Treating Claude Code as a writing operating system rather than a coding tool unlocks the full power of skills, agents, and plugins for content-first workflows.
Build the lead magnet live on screen.
The most powerful thing in this video is not a slash command -- it is the Notion cheat sheet sitting on screen for ten straight minutes while Alex demoed other things.
- Open with this is not for devs, it is for your audience -- one sentence that makes the right people lean in and everyone else self-filter.
- Use your real system as the demo. Show your actual file tree, your actual agents, your actual token counts. No mock-ups.
- Build your lead magnet inside the session you are recording. The audience watches it get made, which is more persuasive than any sales copy.
- Keep a sticky prop pinned in the corner for the entire runtime. Silent CTA for every minute of watch time.
- The /context MCP-cost reveal is a repeatable format: run a diagnostic, surface the surprising number, explain why it matters. Works for any tool with hidden overhead.
Terms worth knowing.
- /context command
- A Claude Code slash command that displays a visualization of everything currently loaded into the context window, showing what files and instructions are consuming space.
- /stats command
- A Claude Code slash command that shows usage statistics for the current session, including token counts, API calls, and cost information.
- /plugins command
- A Claude Code slash command that lists available extensions or integrations active in the current session, helping users manage their tool ecosystem.
- context window
- The maximum amount of text — files, instructions, conversation history — an AI model can process at once, measured in tokens; quality degrades when it fills up.
- context profile
- A JSON file containing structured information about a business, voice, ideal client, or project that is loaded into Claude Code sessions to provide persistent background context.
- knowledge base
- A curated folder of documents, summaries, and reference material that Claude Code reads from to answer questions and generate content with accurate, personalized context.
- Claude skill
- A reusable, self-contained automation script that extends Claude Code's capabilities to perform a specific task, such as publishing a newsletter or generating visual assets.
- writing system
- Alex McFarland's term for the full Claude Code setup — agents, context profiles, knowledge base, skills — configured specifically for content creation rather than software development.
Things they pointed at.
Lines you could clip.
“Unlike all of the other creators out there, I really wanna focus on three that I think make the biggest impact on writers and content creators.”
“The MCP tools take up so much. They take up 21.6%. I was also pretty surprised to see that the agents only take up 0.1%.”
“I really have the $200 a month max plan, and I never even get close to running into limits, and I work all day long inside of Claude code.”
“Non generic AI aesthetics, which everybody is getting tired of and which is pretty pretty terrible at this point.”
Word for word.
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.
The bait, then the rug-pull.
Anthropic dropped ten-plus updates in one cycle. Alex McFarland ignored nine of them. What he kept -- /context, /stats, /plugins -- is a three-command toolkit for writers who use Claude Code as a writing system, not a compiler. This is the non-developer briefing the rest of YouTube skipped.
Named ideas worth stealing.
Context Window Audit
- System prompt
- System tools
- MCP tools
- Custom agents
- Memory files
- Messages
- Free space
Run /context to see token consumption by category. MCPs often surprise -- each installed server loads ALL its tool definitions into context even if unused in-session.
Project-scope vs Global plugin install
Install plugins at project scope to keep different client projects clean. Global installs bleed context into every future session.
How they asked for the click.
“If you are not subscribed to my Substack or YouTube, make sure to do that. Paid subscribers get access to this Claude Code cheat sheet.”
Soft and earned. The cheat sheet has been on screen for 10 minutes. By the time the CTA hits the viewer already knows what they want.










































































