Jonathon's AI Wiki

Nine Claude Code Plugins to Build 10× Faster

8 min read

Source: raw/9_Claude_Code_Plugins_to_Build_10x_Faster.md (YouTube transcript, sBF3UumkL4Y, fetched 2026-05-15). Higgsfield sponsorship disclosed in the source.

A curated list of nine Claude Code plugins that the creator runs daily to “build 10× faster and save money in the process.” The framing is consistent: every plugin either (a) cuts the token cost of mechanical work (Caveman, Morph, Code Burn), (b) extends Claude Code’s reach into surfaces it can’t natively touch (Firecrawl+Exa, Higgsfield, Anthropic’s official set, Codex), or (c) imposes a structured workflow on top of vibe-coded sessions (Compound Engineering, BuildPartner). Pairs with the W21 release-digest economics — the claude --print SDK credit-split on June 15 makes every “save tokens” plugin below materially more valuable.

Key Takeaways

  • Caveman is the cheapest single-plugin token win — forces Claude to respond like a caveman, cutting filler and lowering per-turn cost. Sponsor-style framing aside, this is just “concise mode” enforced via skill.
  • Firecrawl + Exa is a two-plugin stack covering the gaps in Claude’s native web fetch: Exa for semantic discovery (vs Claude’s keyword match), Firecrawl for cleaned JS-rendered page content. The “AI output is only as good as the input you provide” thesis is the operator framing for stacking them.
  • Compound Engineering packages the plan → work → review → compound → repeat five-step loop into a single skill. The creator credits this loop with launching a $481,000 vibe-coded product. Maps onto Printing Press / Routines and Hermes-style self-improving loops.
  • Higgsfield MCP (sponsored disclosure in source) extends Claude Code with image and video generation by connecting Higgsfield’s MCP server. Two use-cases highlighted: “content agency killer” (generate landing-page images + UGC-style ad-creative video using existing project context — brand guidelines, target audience already known) and competitor-research → trending-format gap → content generation in a single Claude conversation.
  • Anthropic’s official plugins are biased toward by the creator because “the maintainer of a plugin matters.” Recommended set: skill-creator (streamlines skill creation), legal (boilerplate legal-doc surface), frontend-design (/front-end-design make six variants of my landing page optimized for conversion → click through to pick components), security-guidance (DIY pre-launch security audit). See Anthropic Skills Repo and Design Skills Overview.
  • OpenAI’s Codex plugin for Claude Code is the multi-model demonstration — OpenAI shipped its own plugin that routes Claude Code’s UX through GPT-5.5 via Codex. The creator’s framing: (1) different models are better at different things (multi-doctor analogy), (2) “model independence is a muscle worth flexing” against subsidy reversal. Cost claim: 1,800/mo of actual token consumption — the gap is VC subsidy. Use case: /codex:rescue when Claude is stuck. Matches the W21 harness-portability framing from Sigrid Jin (harness + model are swap-replaceable, context is the asset that compounds).
  • buildpartner.ai is the creator’s own plugin. Two surfaces: /bp expert-advice pulls expert frameworks for the current task (positioned as “remove uncertainty so you stop second-guessing” — the McKinsey-without-the-bill angle); skill-improve sets up recursive feedback loops on the project’s own skill library so it improves automatically over time. Same self-improving-system pattern as Hermes / Compound Engineering / 00-resources AIOS layouts.
  • Morph is the technical-performance plugin. Three sub-features: fast-apply (file edits ~8× faster, ~90% cheaper), warp-grep (codebase search 50% cheaper, 28% faster), compact (session compression saves 5–15 minutes). The creator’s framing: “most token spend is on mechanical work, not reasoning — Morph cuts the mechanical waste.” Source notes the speed figures are vendor-published and hard to verify directly, but matches anecdotal experience. Cost: paid plugin.
  • Code Burn is the spend-visibility dashboard. code burn → o produces a list of token-save suggestions; paste into Claude Code to apply. The author’s screenshot shows 200/mo Claude Max plan — same subsidy-reversal framing as the Codex plugin entry.
  • Stack interaction matters more than any single plugin. Caveman + Morph + Code Burn forms a token-spend stack; Firecrawl + Exa + Higgsfield forms a media+research extension stack; Compound Engineering + BuildPartner + Anthropic-official forms a discipline stack. The video’s closing claim — “stack all nine and you’ll entirely level up your experience” — is the operator framing for picking from columns rather than picking one.

The five-step Compound Engineering loop

Quoted from the source as the framing for why structured workflow plugins exist:

  1. Plan the feature you’re working on — what exactly do you want it to do?
  2. Use AI to do the work based on the plan from step 1.
  3. Have AI review the work and confirm it’s actually effective.
  4. Compound — the AI learns from steps 1–3 so it doesn’t make the same mistakes.
  5. Repeat.

Step 1 is load-bearing — quoted reference to Boris Cherny (Claude Code creator): “the most important thing you can do is get the plan right.” Maps onto Anthropic’s best-practice docs on Plan-Mode discipline and the CLI plan-mode flags.

Multi-model framing — Codex plugin

The video’s most operator-relevant claim sits inside the Codex plugin segment: “a lot of the models that you use right now are VC-subsidized, which means investors are essentially paying for tokens. So if subsidizing goes away and pricing goes up, I want to be comfortable using different models.”

This matches the W21 release-digest economics — the claude --print SDK credit-split on June 15 and OpenAI’s matching 2-month-free Codex promo are the leading indicators of the subsidy ramp coming off. Treating model + harness as commodities and context as the moat is the long-term hedge ^[inferred].

Cross-cutting cost discipline

Three of the nine plugins (Caveman, Morph, Code Burn) target token cost directly. The implicit recommendation in the source is that any always-on Claude Code workflow should run a Code Burn audit and apply the suggested token-saves before scaling token-consumption further. Pairs with 18 Claude Code Token-Optimization Techniques (which covers 18 broader patterns, not plugin-mediated) and Prompt Caching for Agencies (the agency-side cost-discipline frame).

The Morph “use code instead of AI for repetitive tasks” prompt — quoted in the source — is itself a meta-skill worth lifting:

Based on everything that I use in my Claude code project, is there anything that I can convert to a script that will allow me to use code instead of using AI to complete a task?

Apply once per project to surface the mechanical work that doesn’t need an LLM in the loop.

Try It

  1. Install Caveman first. Lowest-friction token-save win; the verbal tic is the price of admission. Source links the install in the video description.
  2. Then Compound Engineering or BuildPartner. Pick one — both impose structure on vibe-coded sessions. Compound Engineering for the five-step loop discipline; BuildPartner for the “expert advice” surface plus recursive skill-improvement.
  3. Add Firecrawl + Exa together, not individually. Claude native fetch is keyword-matched and SEO-content-prone; Exa does semantic discovery; Firecrawl does cleaned JS-aware fetch. The trio is the stack.
  4. Audit current spend with Code Burn before installing Morph. code burn → o produces a save-suggestion list; apply those first before paying for Morph. If you’re still spending too much after the free suggestions land, Morph’s fast-apply / warp-grep / compact gains make sense to pay for.
  5. Install the four Anthropic-official plugins together. Bias toward maintained tools. Skill-creator + legal + frontend-design + security-guidance is the “trust Anthropic to keep these working” basket.
  6. Try the Codex plugin once per quarter. Same operator hygiene as the W21 harness-portability recommendation from Sigrid Jin — keep cross-harness muscle memory current as cheap insurance against a one-vendor cliff.
  7. Install Higgsfield MCP if you do any landing-page or ad-creative work. Project-context already inside Claude Code becomes a generation prompt without re-stating brand guidelines and audience. See Higgsfield Supercomputer for the wider Higgsfield surface.
  8. Pair this catalog with Six Best Claude Code Skills for Business and Seven Claude Skills That Run My Business — three independent curated lists from this week, useful as a triangulation check on what’s actually load-bearing in production Claude Code workflows.

Open Questions

  • Compound Engineering is a named, installable plugin in the video — what is the install URL and maintainer? The source links the install in the YouTube video description but doesn’t name the repo. Worth a research pass to identify the exact distribution.
  • Morph’s vendor-published speed figures (~8× faster file-edit, 90% cheaper) are not independently verified. Source admits “these are theoretical statistics and it’s a bit hard for me to test this directly.” Worth tracking community benchmarks before recommending the paid plugin to enterprise users.
  • Code Burn’s 200-Max claim is a single-source data point. Matches the Codex plugin’s same framing; one community report on r/ClaudeAI 1tcetsd cites similar gap (see W21 digest --print repricing section). Worth tracking whether the gap narrows post-June-15 SDK-billing split.
  • BuildPartner.ai is the creator’s own product — disclosed, but worth noting independent reviews aren’t yet in the wiki. Flag for follow-up research pass.

Graph View

Backlinks