Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Claude Code used 3x fewer tokens with one change: - Before: 10.4M tokens · 10 errors · $9.21 - After: 3.7M tokens · 0 errors · $2.81 I used Insforge Skills + CLI as the backend context engineering layer for Claude Code (open-source and local). Repo:

Avi Chawla

71,798 subscribers

295,077 görüntüleme • 4 ay önce •via X (Twitter)

Eğitim Haberler & Politika Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Claude Code just got a memory upgrade. And it’s kind of insane. A free tool called Claude Mem lets Claude remember everything across sessions. The result? Up to 95% fewer tokens used. Which means faster workflows and way cheaper AI automation. This fixes Claude Code’s biggest weakness.

Claude Code just got a memory upgrade. And it’s kind of insane. A free tool called Claude Mem lets Claude remember everything across sessions. The result? Up to 95% fewer tokens used. Which means faster workflows and way cheaper AI automation. This fixes Claude Code’s biggest weakness.

Julian Goldie SEO

11,989 görüntüleme • 5 ay önce

Meet Higgsfield CLI + Marketing Skills. Instead of burning tokens on bloated schemas, or shipping broken creative at scale, the CLI keeps agent spend lean and Skills keep output high quality. Pairs with Сodex, Claude Code, Openclaw etc. npx skills add higgsfield-ai/skills

Meet Higgsfield CLI + Marketing Skills. Instead of burning tokens on bloated schemas, or shipping broken creative at scale, the CLI keeps agent spend lean and Skills keep output high quality. Pairs with Сodex, Claude Code, Openclaw etc. npx skills add higgsfield-ai/skills

Higgsfield AI 🧩

338,332 görüntüleme • 3 ay önce

I cut Fable 5 token usage 2.5x with just one change! - Before: 5.5 M tokens · 7 errors · $8.94 - After: 2.3 M tokens · 0 errors · $4.17 The final build was the same for both, but the path the agent took wildly differed. In both runs, the agent started with the same thing, i.e., it understood the backend before building anything, like: - Permission policies - Available storage buckets - Auth providers configured - How edge functions are deployed The first run used Firebase, which was built for a human dev using a dashboard. While the dev can read the above state by clicking through tabs, an agent has no dashboard. So it gathered the same info through API calls. And there's no single Firebase call that returned this info. The agent required to query multiple times, and each query over-returned. For instance, when the agent asked how sign-in is configured, Firebase also returned the entire auth surface and every method it supported. This was far more context than what it needed. And it repeated across every part of the backend it inspected. Some states (like which auth providers are active) weren't queryable at all. I provided it myself. Otherwise, the agent would have guessed. Errors further compounded the token usage. When a dev sees "permission denied," they can look at the console and figure out whether it's a rule, a path, or an unauthenticated request. Firebase returned the same string to the agent as well, and it had none of that surrounding context to debug. So it guessed again, picked the most likely cause, and rewrote code, utilizing more tokens. This Firebase setup cost me 5.5M tokens and 7 manual interventions during errors on a full-stack RAG app. But I brought that down to 2.3M tokens and 0 manual interventions by using InsForge as the backend context engineering layer (open-source and self-hostable via Docker). It provides the same primitives as Supabase/Firebase, but structures the entire information layer for agents, instead of dashboards. In one CLI call that consumed ~500 tokens, the agent saw the full backend topology before writing a single line of code. This included auth, database, storage, edge functions, model gateway, micro VMs, and deployment. Also, instead of loading the entire product surface into context on every task, four narrowly scoped skills activated only when relevant to keep cognitive load minimal. And to ensure efficient retries if needed, every CLI operation returned structured JSON with meaningful exit codes, so the agent never guessed what to do next. Here's the InsForge GitHub Repo: (don't forget to star it ⭐) The video below depicts the final build, comparing Firebase and InsForge. To dive deeper, I recently published a full walkthrough building the same RAG app on both backends and inspected them end-to-end. Read it below.

I cut Fable 5 token usage 2.5x with just one change! - Before: 5.5 M tokens · 7 errors · $8.94 - After: 2.3 M tokens · 0 errors · $4.17 The final build was the same for both, but the path the agent took wildly differed. In both runs, the agent started with the same thing, i.e., it understood the backend before building anything, like: - Permission policies - Available storage buckets - Auth providers configured - How edge functions are deployed The first run used Firebase, which was built for a human dev using a dashboard. While the dev can read the above state by clicking through tabs, an agent has no dashboard. So it gathered the same info through API calls. And there's no single Firebase call that returned this info. The agent required to query multiple times, and each query over-returned. For instance, when the agent asked how sign-in is configured, Firebase also returned the entire auth surface and every method it supported. This was far more context than what it needed. And it repeated across every part of the backend it inspected. Some states (like which auth providers are active) weren't queryable at all. I provided it myself. Otherwise, the agent would have guessed. Errors further compounded the token usage. When a dev sees "permission denied," they can look at the console and figure out whether it's a rule, a path, or an unauthenticated request. Firebase returned the same string to the agent as well, and it had none of that surrounding context to debug. So it guessed again, picked the most likely cause, and rewrote code, utilizing more tokens. This Firebase setup cost me 5.5M tokens and 7 manual interventions during errors on a full-stack RAG app. But I brought that down to 2.3M tokens and 0 manual interventions by using InsForge as the backend context engineering layer (open-source and self-hostable via Docker). It provides the same primitives as Supabase/Firebase, but structures the entire information layer for agents, instead of dashboards. In one CLI call that consumed ~500 tokens, the agent saw the full backend topology before writing a single line of code. This included auth, database, storage, edge functions, model gateway, micro VMs, and deployment. Also, instead of loading the entire product surface into context on every task, four narrowly scoped skills activated only when relevant to keep cognitive load minimal. And to ensure efficient retries if needed, every CLI operation returned structured JSON with meaningful exit codes, so the agent never guessed what to do next. Here's the InsForge GitHub Repo: (don't forget to star it ⭐) The video below depicts the final build, comparing Firebase and InsForge. To dive deeper, I recently published a full walkthrough building the same RAG app on both backends and inspected them end-to-end. Read it below.

Avi Chawla

113,219 görüntüleme • 2 ay önce

I burned $13,836 worth of Claude Code tokens in June. The same work on open models: $3,106. That's $10,730 left on the table — one month, one laptop. So I built the instrument that shows you the gap. Open source, 100% local. Launching today 🧵

I burned $13,836 worth of Claude Code tokens in June. The same work on open models: $3,106. That's $10,730 left on the table — one month, one laptop. So I built the instrument that shows you the gap. Open source, 100% local. Launching today 🧵

Dennison

62,260 görüntüleme • 1 ay önce

This GitHub repo is gold for anyone running Claude Code/ Codex / Any coding agent at all. My usage limits almost last double since I started using this. An open source context layer that stops your agent from reading 40 files to answer one question. No API key, no billing, no rate limit tiers. Benchmarked against Claude Code baseline: 27x token efficiency, 36% lower cost, 89% fewer file reads, 49% fewer tool calls. Every number is reproducible, the harness is in the repo. 3.5k+ stars. 50k+ pip installs, 30+ contributors, works with Claude Code, Cursor and VS Code out of the box. pip install repowise and point it at your codebase.

This GitHub repo is gold for anyone running Claude Code/ Codex / Any coding agent at all. My usage limits almost last double since I started using this. An open source context layer that stops your agent from reading 40 files to answer one question. No API key, no billing, no rate limit tiers. Benchmarked against Claude Code baseline: 27x token efficiency, 36% lower cost, 89% fewer file reads, 49% fewer tool calls. Every number is reproducible, the harness is in the repo. 3.5k+ stars. 50k+ pip installs, 30+ contributors, works with Claude Code, Cursor and VS Code out of the box. pip install repowise and point it at your codebase.

Srishti

12,998 görüntüleme • 1 ay önce

Introducing InsForge 2.0: The Backend for Agentic Development Our OSS backend provides databases, auth, storage, model gateway, and edge functions accessible through a context-optimized layer that agents can better understand and operate end-to-end. GitHub: Key Benchmarks (vs. Supabase MCP): - 14% higher accuracy - 1.3x faster per task - 2.4x fewer tokens Better. Faster. Cheaper. Build features more quickly and confidently — all at 41.7% of the cost. Shipping your ideas today. $ npx @insforge/cli create

Introducing InsForge 2.0: The Backend for Agentic Development Our OSS backend provides databases, auth, storage, model gateway, and edge functions accessible through a context-optimized layer that agents can better understand and operate end-to-end. GitHub: Key Benchmarks (vs. Supabase MCP): - 14% higher accuracy - 1.3x faster per task - 2.4x fewer tokens Better. Faster. Cheaper. Build features more quickly and confidently — all at 41.7% of the cost. Shipping your ideas today. $ npx @insforge/cli create

InsForge

1,592,532 görüntüleme • 5 ay önce

10 GitHub repos with ⭐ 450k+ combined stars that stop your agent from wasting tokens 1. caveman 98k⭐ - makes your AI agent talk like a caveman. Same answers, 65% fewer output tokens. 2. rtk 76k⭐ - CLI proxy that filters git/test/docker output before it hits your context. Up to 90% less bash noise. 3. mem0 63k⭐ - memory layer for AI agents. Stops your agent from re-explaining the same context every session. 4. context7 60.7k⭐ - pulls exact, up-to-date docs into context instead of your agent guessing and burning tokens on retries. 5. aider 48k⭐ - builds a map of your repo instead of loading the whole codebase into context. 6. code-review-graph 30k⭐ - graphs your codebase so your agent reads 2-3 files instead of the whole repo. Up to 376x fewer tokens per question. 7. serena 28k⭐ - gives agents symbol-level code access instead of reading full files line by line. 8. repomix 28k⭐ - compresses your entire repo into an AI-friendly format. ~70% token reduction. 9. ccusage 18k⭐ - shows you exactly where your Claude Code sessions are burning tokens. 10. GPTCache 8k⭐ - semantic cache for LLM calls. Stop paying twice for the same question. Save this before your next agent session burns through your subscription 👇

10 GitHub repos with ⭐ 450k+ combined stars that stop your agent from wasting tokens 1. caveman 98k⭐ - makes your AI agent talk like a caveman. Same answers, 65% fewer output tokens. 2. rtk 76k⭐ - CLI proxy that filters git/test/docker output before it hits your context. Up to 90% less bash noise. 3. mem0 63k⭐ - memory layer for AI agents. Stops your agent from re-explaining the same context every session. 4. context7 60.7k⭐ - pulls exact, up-to-date docs into context instead of your agent guessing and burning tokens on retries. 5. aider 48k⭐ - builds a map of your repo instead of loading the whole codebase into context. 6. code-review-graph 30k⭐ - graphs your codebase so your agent reads 2-3 files instead of the whole repo. Up to 376x fewer tokens per question. 7. serena 28k⭐ - gives agents symbol-level code access instead of reading full files line by line. 8. repomix 28k⭐ - compresses your entire repo into an AI-friendly format. ~70% token reduction. 9. ccusage 18k⭐ - shows you exactly where your Claude Code sessions are burning tokens. 10. GPTCache 8k⭐ - semantic cache for LLM calls. Stop paying twice for the same question. Save this before your next agent session burns through your subscription 👇

unicode

65,080 görüntüleme • 5 gün önce

Introducing the Firecrawl Skill + CLI for Agents 🔥 Agents like Claude Code, Codex, and OpenCode need live quality context from the web. The CLI pulls web content to local files with bash-powered search for the highest token efficiency. $ npx skills add firecrawl/cli

Introducing the Firecrawl Skill + CLI for Agents 🔥 Agents like Claude Code, Codex, and OpenCode need live quality context from the web. The CLI pulls web content to local files with bash-powered search for the highest token efficiency. $ npx skills add firecrawl/cli

Firecrawl

87,256 görüntüleme • 6 ay önce

UI Skills are now easier for agents. Introducing UI Skills CLI. ask Codex, Cursor, Claude Code, or any agent to use the CLI, like: "use `npx ui-skills start` to fix the motion in this dialog" it finds the best design-engineering skill for the job and uses it as context

UI Skills are now easier for agents. Introducing UI Skills CLI. ask Codex, Cursor, Claude Code, or any agent to use the CLI, like: "use `npx ui-skills start` to fix the motion in this dialog" it finds the best design-engineering skill for the job and uses it as context

Ibelick

61,422 görüntüleme • 2 ay önce

Introducing watchmen. It writes the skill files your coding agents should already have from your own sessions, shared across Claude Code, Codex, and pi, so you stop paying tokens to re-explain what your agent learned last week. Local and open-source.

Introducing watchmen. It writes the skill files your coding agents should already have from your own sessions, shared across Claude Code, Codex, and pi, so you stop paying tokens to re-explain what your agent learned last week. Local and open-source.

Dria

43,967 görüntüleme • 3 ay önce

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

Ado

71,910 görüntüleme • 6 ay önce

Peter Steinberger Quietly Started A Shift That Makes Claude 35x Cheaper To Run The way Claude Code talks to tools matters more than people think. Most use MCP, and it quietly eats tokens, it loads everything into context every time, even tools you never call. One benchmark: MCP burned 35x more tokens than a CLI on the same task. Peter Steinberger, the OpenClaw guy, got annoyed by this and started building lean CLIs himself. That kicked off a tool called Printing Press. You point Claude Code at any website, even ones with no API like ESPN or Craigslist, and it builds a small command tool for it in about 10 minutes. In one demo, a request pulled 132,000 tokens of raw data, but the tool processed it locally and only handed Claude a 2,000-token summary. The rest never touched the context window. It also comes with ~50 ready-made tools you can grab right away. To start, point Claude Code at the links from and ask it to set it up. Bookmark this.

Peter Steinberger Quietly Started A Shift That Makes Claude 35x Cheaper To Run The way Claude Code talks to tools matters more than people think. Most use MCP, and it quietly eats tokens, it loads everything into context every time, even tools you never call. One benchmark: MCP burned 35x more tokens than a CLI on the same task. Peter Steinberger, the OpenClaw guy, got annoyed by this and started building lean CLIs himself. That kicked off a tool called Printing Press. You point Claude Code at any website, even ones with no API like ESPN or Craigslist, and it builds a small command tool for it in about 10 minutes. In one demo, a request pulled 132,000 tokens of raw data, but the tool processed it locally and only handed Claude a 2,000-token summary. The rest never touched the context window. It also comes with ~50 ready-made tools you can grab right away. To start, point Claude Code at the links from and ask it to set it up. Bookmark this.

Ridark

32,351 görüntüleme • 1 ay önce

someone just rebuilt claude code in pure python and made it 230x cheaper to run it's called clawcodex. a full from-scratch port of the claude code agent loop. 230k+ lines of python, MIT licensed it keeps your request prefix byte-stable, so DeepSeek's prompt cache covers your entire system + tools + history on every turn cache-hit input then bills at ~$0.0435 per 1M tokens the same 1M tokens on Claude Fable 5 runs you $10 so the longer you code, the more the cache pays off what you actually get: → 25 LLM providers (Claude, GPT, DeepSeek, GLM, local ollama) → 1M token context window → real agent loop: tools, skills, REPL, session history → one-line install, mac/linux/wsl and it's sitting at 677 stars. basically nobody is looking yet bookmark this before it gone

someone just rebuilt claude code in pure python and made it 230x cheaper to run it's called clawcodex. a full from-scratch port of the claude code agent loop. 230k+ lines of python, MIT licensed it keeps your request prefix byte-stable, so DeepSeek's prompt cache covers your entire system + tools + history on every turn cache-hit input then bills at ~$0.0435 per 1M tokens the same 1M tokens on Claude Fable 5 runs you $10 so the longer you code, the more the cache pays off what you actually get: → 25 LLM providers (Claude, GPT, DeepSeek, GLM, local ollama) → 1M token context window → real agent loop: tools, skills, REPL, session history → one-line install, mac/linux/wsl and it's sitting at 677 stars. basically nobody is looking yet bookmark this before it gone

alex

158,729 görüntüleme • 15 gün önce

someone just rebuilt claude code in pure python and made it ~230x cheaper to run it's called clawcodex. a full from-scratch port of the claude code agent loop. 230k+ lines of python, MIT licensed it keeps your request prefix byte-stable, so DeepSeek's prompt cache covers your entire system + tools + history on every turn cache-hit input then bills at ~$0.0435 per 1M tokens the same 1M tokens on Claude Fable 5 runs you $10 so the longer you code, the more the cache pays off what you actually get: → 25 LLM providers (Claude, GPT, DeepSeek, GLM, local ollama) → 1M token context window → real agent loop: tools, skills, REPL, session history → one-line install, mac/linux/wsl and it's sitting at 677 stars. basically nobody is looking yet bookmark this before it gone

someone just rebuilt claude code in pure python and made it ~230x cheaper to run it's called clawcodex. a full from-scratch port of the claude code agent loop. 230k+ lines of python, MIT licensed it keeps your request prefix byte-stable, so DeepSeek's prompt cache covers your entire system + tools + history on every turn cache-hit input then bills at ~$0.0435 per 1M tokens the same 1M tokens on Claude Fable 5 runs you $10 so the longer you code, the more the cache pays off what you actually get: → 25 LLM providers (Claude, GPT, DeepSeek, GLM, local ollama) → 1M token context window → real agent loop: tools, skills, REPL, session history → one-line install, mac/linux/wsl and it's sitting at 677 stars. basically nobody is looking yet bookmark this before it gone

Argona

51,369 görüntüleme • 1 ay önce

Built a Skool clone with Claude Code (Opus 4.5), with auth, db + storage with the new web app builder. (Launching next week). We are building the easiest way to use the most powerful coding model (Claude Code) in the world to build mobile apps and web apps. No performative hour long agent runs that waste tokens. Just raw Claude Code running in a sandbox, pre built with skills that make frontend + backend just work. Let me know if you want to beta test.

Built a Skool clone with Claude Code (Opus 4.5), with auth, db + storage with the new web app builder. (Launching next week). We are building the easiest way to use the most powerful coding model (Claude Code) in the world to build mobile apps and web apps. No performative hour long agent runs that waste tokens. Just raw Claude Code running in a sandbox, pre built with skills that make frontend + backend just work. Let me know if you want to beta test.

Riley Brown

51,044 görüntüleme • 7 ay önce

Opus 4.8 for planning 🤝 GPT 5.5 for implementation Claude is a nicer conversation and /grilling partner than Codex in my experience, but GPT 5.5 on low cranks out higher quality code in fewer tokens. Here's how I divide up the work:

Opus 4.8 for planning 🤝 GPT 5.5 for implementation Claude is a nicer conversation and /grilling partner than Codex in my experience, but GPT 5.5 on low cranks out higher quality code in fewer tokens. Here's how I divide up the work:

Ben Holmes

23,115 görüntüleme • 2 ay önce

ANTHROPIC JUST LOST 20,000 CLAUDE CODE USERS TO ONE GITHUB REPO. 20,000 devs. 26k stars. 4,000 forks. 10 free models. COMPLETELY FREE. Bookmark this before Anthropic notices. Your Claude Code bill will start working differently. It reroutes Claude Code to DeepSeek, Kimi, and 8 more same CLI, different model behind it. 5 min setup. $200/mo saved. 0 downgrade on small tasks. swap the endpoint in your config today. Link below. Claude Code → Endpoint swap → Free models → No bill → Money

ANTHROPIC JUST LOST 20,000 CLAUDE CODE USERS TO ONE GITHUB REPO. 20,000 devs. 26k stars. 4,000 forks. 10 free models. COMPLETELY FREE. Bookmark this before Anthropic notices. Your Claude Code bill will start working differently. It reroutes Claude Code to DeepSeek, Kimi, and 8 more same CLI, different model behind it. 5 min setup. $200/mo saved. 0 downgrade on small tasks. swap the endpoint in your config today. Link below. Claude Code → Endpoint swap → Free models → No bill → Money

AdiiX

418,743 görüntüleme • 1 ay önce

Skills shopping cart for Claude Code In this video I show how I add Railway Skills to a “shopping cart”. After selecting the Skills I need, I copy a single command and they’re added directly to my project. I built to make the composition of Claude Code components as flexible as possible. You can install settings, hooks, subagents, and anything new that gets added to Claude Code will appear on the site. It’s fully open source and community-maintained. If you want to contribute, you’re welcome to fix or update components, download and use the existing ones, or simply support the project by leaving a star on GitHub. Repo:

Skills shopping cart for Claude Code In this video I show how I add Railway Skills to a “shopping cart”. After selecting the Skills I need, I copy a single command and they’re added directly to my project. I built to make the composition of Claude Code components as flexible as possible. You can install settings, hooks, subagents, and anything new that gets added to Claude Code will appear on the site. It’s fully open source and community-maintained. If you want to contribute, you’re welcome to fix or update components, download and use the existing ones, or simply support the project by leaving a star on GitHub. Repo:

Daniel San

20,460 görüntüleme • 7 ay önce

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Morty

136,663 görüntüleme • 2 ay önce

$THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this$

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,177 görüntüleme • 2 ay önce