agentic-stack (.agent/ folder) vs RTK (Rust Token Killer)
Both in the memory & context category. Side-by-side — pick the one that fits your stack tonight.
One portable folder of memory + skills that works across every AI agent tool.
- rating
- 3★
- tested
- —
- cost
- free
- install
- drop-in
- stars
- 1,357
- updated
- 5d ago
You only use one agent tool and never plan to switch.
Stops Claude from wasting tokens on terminal junk. 60-90% cheaper per session.
- rating
- 4★
- tested
- —
- cost
- free
- install
- drop-in
- stars
- 31,988
- updated
- 5d ago
Your sessions are short enough that token cost doesn't matter to you.
why it matters · agentic-stack (.agent/ folder)
Your agent's memory, skills, and workflows usually get locked to whichever tool you started with — Claude Code, Cursor, Windsurf, whatever. Switch tools and you start over from zero. agentic-stack is a simple `.agent/` folder structure that holds everything — memory, skill files, protocols — in one place. Drop it in any project and every major agent tool reads from it. Swap Claude Code for Cursor next month and your lessons come with you.
why it matters · RTK (Rust Token Killer)
Every time Claude Code runs a command in your terminal — a git status, an npm install, a test suite — the whole output gets fed back to the AI. That's usually the most token-hungry part of any session, and most of it is junk Claude doesn't need. RTK sits between your terminal and Claude, strips the junk, passes the meaningful bits through. On common dev commands you save 60-90% per run. One binary, no config, free.