15 open source tools compared. Sorted by stars. Scroll down for our analysis.
| Tool | Stars | Velocity | Score |
|---|---|---|---|
everything-claude-code The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. | 179.8k | +5672/wk | 86 |
gstack Use Garry Tan's exact Claude Code setup: 15 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA | 94.1k | +4109/wk | 91 |
caveman 🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman | 58.5k | +3779/wk | 86 |
career-ops AI-powered job search system built on Claude Code. 14 skill modes, Go dashboard, PDF generation, batch processing. | 44.2k | +1292/wk | 83 |
codex-plugin-cc Use Codex from Claude Code to review code or delegate tasks. | 18.3k | +638/wk | 83 |
skills Claude Code skills based on The Minimalist Entrepreneur by Sahil Lavingia | 8.6k | +104/wk | 75 |
prompt-master A Claude skill that writes the accurate prompts for any AI tool. Zero tokens or credits wasted. Full context and memory retention | 7.4k | +184/wk | 82 |
gsd-2 A powerful meta-prompting, context engineering and spec-driven development system that enables agents to work for long periods of time autonomously without losing track of the big picture | 7.4k | +228/wk | 80 |
claude-obsidian Claude + Obsidian knowledge companion. Persistent, compounding wiki vault based on Karpathy's LLM Wiki pattern. /wiki /save /autoresearch | 4.8k | +469/wk | 73 |
dbskill dontbesilent 的商业诊断 Skills for Claude Code | 4.6k | +409/wk | 59 |
awesome-codex-subagents A collection of 130+ specialized Codex subagents covering a wide range of development use cases. | 4.6k | +116/wk | 78 |
chrome-cdp-skill Give your AI agent access to your live Chrome session — works out of the box, connects to tabs you already have open | 3.0k | +25/wk | 74 |
diagram-design Thirteen editorial diagram types for Claude Code. Self-contained HTML + SVG. No shadows, no Mermaid-slop. | 2.3k | +95/wk | 61 |
wewrite 公众号文章全流程 AI Skill for Claude Code — 热点抓取 → 选题 → 写作 → SEO → 视觉AI → 排版 → 微信草稿箱 | 1.9k | +103/wk | 67 |
chromex A Codex-powered Chrome side-panel assistant for page context, tabs, voice, and image workflows. | 1.1k | +237/wk | 67 |
Stay ahead of the category
New tools and momentum shifts, every Wednesday.
This is a curated collection of configuration patterns: CLAUDE.md templates, skills, memory structures, security practices, and prompt engineering techniques. Consider it a performance tuning guide for AI-assisted development. MIT licensed, JavaScript. The repo covers agent harness optimization: how to structure your CLAUDE.md for better context, how to write reusable skills, how to set up memory that persists between sessions, and security patterns to prevent prompt injection. It's not a tool you install. It's a reference architecture you adapt to your workflow. Completely free. The repo is MIT licensed and the content is openly available. The ecc.tools website appears to offer additional resources but the core value is in the GitHub repo itself. Solo AI-assisted developers: this is the target audience. If you're using Claude Code, Codex, Cursor, or similar agents and haven't optimized your configuration, there are real gains here. Teams: useful as a starting template for standardizing agent configurations across developers. The catch: this is a knowledge repo, not software. It's only as good as you make it. You need to read, understand, and adapt the patterns to your specific workflow. The star count is massive but the actual value depends on whether you're already using AI coding agents. If you're not, this is irrelevant. If you are, the CLAUDE.md patterns and skill structures alone are worth the read.
GStack gives you 15 opinionated tools and 9 workflow skills that do exactly that. Install it, and suddenly your terminal has slash commands for code review, shipping, browser automation, QA testing, and retrospectives. Garry Tan (YC CEO) built this for his own workflow and claims 10K lines of code and 100 PRs per week using it, in weeks. The tools include a persistent Chromium browser daemon for visual testing, plan review that catches issues before you write code, and one-command deploys. Everything lives inside .claude/; nothing touches your PATH, nothing runs in the background except the browser daemon. TypeScript core with some Go for performance. The catch: this is one person's extremely opinionated workflow. If your development style doesn't match Garry's, you'll fight the tools instead of using them. And it's Claude Code only: no Cursor, no Codex, no other agent.
Caveman strips the fluff from Claude Code responses. Install it with one command, activate with /caveman, and your AI assistant drops the pleasantries, hedging, and filler words while keeping full technical accuracy. Average savings: 65% fewer output tokens. Three intensity levels: Lite keeps it professional but terse, Full drops articles and uses fragments, Ultra goes telegraphic. Code blocks, error messages, git commits, and technical terms pass through untouched. Only the natural language gets compressed. A companion tool (caveman-compress) rewrites your CLAUDE.md and memory files to cut input tokens too. Works across 40+ AI coding agents, not just Claude Code. Cursor, Copilot, Windsurf, Cline, Codex, all supported. Heavy token users will feel the difference in both speed and cost. The catch: it started as a meme (Kevin from The Office) but the benchmarks are real, backed by a 2026 arxiv paper. Ultra mode can be hard to read. And the savings are output tokens only, so your thinking/reasoning costs stay the same.
Career-Ops turns Claude Code into a full job search command center. Paste a job URL, get a structured A-F evaluation against your CV with weighted scoring across 10 dimensions. It generates tailored, ATS-optimized PDF resumes per application. One developer used it to evaluate 740+ offers and land a Head of Applied AI role. The system gets smarter over time. It builds an interview story bank in STAR format, scans 45+ pre-configured company portals (Anthropic, OpenAI, Vercel, n8n), and can batch-evaluate 10+ offers in parallel using sub-agents. The Go-based TUI dashboard lets you browse your entire pipeline from the terminal. Solo job seekers who already pay for Claude Code: this is a force multiplier. It does not replace your judgment, it structures it. The human-in-the-loop design means AI evaluates, you decide. The catch: requires a Claude Code subscription to function, so "free" comes with a real asterisk. The pre-configured portals lean heavily toward AI and tech companies. First evaluations are rough until you feed it enough context about yourself.
OpenAI's Codex agent packaged as a Claude Code skill plugin. It lets you invoke Codex from inside Claude Code to review code or delegate tasks, connecting two AI coding agents so they can collaborate. Useful if you want a second opinion from a different model without switching tools. The integration is straightforward: install the skill, and you can ask Claude Code to hand off specific tasks to Codex. Code review is the primary use case, where having two different models look at the same code catches more issues than either alone. The catch: requires both Claude Code and OpenAI API access, so you're paying for two AI services to talk to each other. The value proposition only makes sense if you're already invested in both ecosystems. For most developers, one AI coding tool is enough.
This turns Sahil Lavingia's entire Minimalist Entrepreneur methodology into executable Claude Code skills. Nine skills you install in your terminal: validate your idea, scope an MVP, find first customers, set pricing, and more. Instead of reading a book and trying to apply it, you invoke a skill and your AI walks through Sahil's exact framework applied to your specific situation. It's interactive: it asks you questions, processes your answers, and gives you structured output. The skills are well-structured and the methodology is proven (Gumroad was built on it). The catch: this is a business methodology, not a technical tool. The quality of the output depends entirely on how good your inputs are. And it's one person's framework; if you disagree with the minimalist approach, you'll disagree with the advice. No pricing page for the skills themselves: they're free, but the book is $17 on Amazon if you want the full context.
Prompt Master writes the prompts for you. It's a Claude Code skill that generates accurate, context-aware prompts for any AI tool, optimized so you waste fewer tokens and get better output on the first try. The value proposition is simple: instead of trial-and-error with different prompt phrasings, you describe what you want and Prompt Master generates the prompt that actually works. It retains full context and memory across your session, so each prompt builds on what came before. MIT licensed. The catch: this is a skill that writes prompts for other AI tools, so you're adding an extra LLM call before every interaction. If your prompts are already working fine, this is overhead. And 'accurate prompts' is a bold claim. Prompt engineering is still more art than science, and what works for one model may not work for another.
GSD-2 is a framework for keeping AI agents on track through long, complex tasks by giving them structured context and spec-driven goals. If you've used AI coding agents and watched them lose the plot halfway through a big refactor, this is the fix. The core idea is 'context engineering': you define specs that describe what the agent should build, break work into phases, and the framework ensures the agent always has the right information at the right time. Specs look like structured documents with acceptance criteria, constraints, and dependencies. Instead of the agent drowning in its own conversation history, GSD-2 feeds it focused context windows that keep each step scoped and grounded. The catch: growing fast, but the API is still evolving. Docs are catching up. This is a bet on a concept (structured agent orchestration) rather than a stable production tool. If you need something battle-tested today, look at established agent frameworks. If you want to experiment with the next wave of agent reliability, this is worth watching.
Claude Obsidian turns your Obsidian vault into an autonomous knowledge engine powered by Claude Code. Instead of passive AI chat, it actively reads sources you drop in, extracts entities and concepts, creates cross-referenced wiki pages, and maintains a session context cache so the next conversation picks up where you left off. Ten skill commands cover everything from ingestion to vault linting to autonomous web research. Setup is a git clone and a shell script. The vault structure works directly in Obsidian with no plugin conflicts. It supports six wiki modes (Website, GitHub, Business, Personal, Research, Book/Course) and runs an 8-category vault linter that catches orphan notes, dead links, stale claims, and missing cross-references. Batch ingestion runs through parallel agents. Solo knowledge workers who already use Obsidian and Claude Code get a structured workflow for turning raw sources into an organized, interlinked wiki. The hot.md context cache is a clever solution to Claude Code's session boundary problem. The catch: you need a Claude Code subscription to run any of it, so it's free software that requires paid infrastructure. Heavy ingestion sessions burn through Claude Code context fast. The quality depends on prompt engineering that could break with model updates.
This is a prompt library that gives Claude structured frameworks for doing it. Picture pre-built consulting templates that turn Claude into a business analyst. What's free: Everything. It's a collection of Claude Code skills (prompt files) you drop into your project. No install, no dependencies, no account. The real value here is the structure. Instead of prompting Claude from scratch every time you need a SWOT analysis or process audit, these skills give it a repeatable framework. The prompts are well-organized and cover common business diagnostics. The catch: it's brand new (almost all growth in the last week), the description is partially in Chinese, and the license is listed as 'Other' which means you should read it before using commercially. The skills are also opinionated. They assume a specific diagnostic methodology that may not match how you work. And since these are just prompt files, the barrier to building your own is low.
This is a curated collection of 130+ subagents you can plug in. It's essentially an app store for Codex, where each subagent handles a specific development task: testing, documentation, security review, database migration, and dozens more. You don't build these yourself. You browse the collection, pick the ones relevant to your workflow, and add them to your Codex setup. It's a community effort to make Codex more useful across different development scenarios. The catch: this is a curated list, not a framework. Quality varies across the 130+ entries. Some are polished, some are experiments. And it's Codex-specific. It doesn't with Claude Code, Cursor, or other AI coding tools.
This skill connects your agent to your live Chrome via the Chrome DevTools Protocol (CDP). Your agent can read pages, click buttons, fill forms, and navigate, in the browser you're already using. The difference from tools like Playwright is that this connects to existing tabs. Your agent can interact with pages where you're already authenticated, see what you see, and do what you'd do manually. MIT licensed, JavaScript. The catch: giving an AI agent access to your live browser session with all your logged-in accounts is a real security consideration. The agent can see everything you can see, including sensitive data in open tabs. There's no permission model beyond 'full access.' And CDP connections can be fragile; Chrome updates can break the protocol.
Diagram-design is a Claude Code skill for editorial-quality diagrams. Architecture sketches, flowcharts, sequence diagrams, quadrants, pyramids. 13 types total, all rendered as self-contained HTML and SVG with no JavaScript or build step. The output is opinionated: low density, restrained color, accent used sparingly on the one or two things that matter. It looks like something a design team made, not generic AI output. Install is clone or plugin, then tell Claude to onboard it to your website and it pulls your brand palette and typography from your homepage. After that every diagram uses your colors. The skill activates automatically when you ask for a diagram. Solo writers and technical bloggers: install it. Small teams with a brand style guide: install it team-wide and onboard to your site. Large teams with a design system: the editorial constraints may conflict with your existing design language, evaluate first. The catch: the plugin route puts the skill in a cache that updates overwrite, so style-guide customizations get wiped unless you clone the repo and symlink. And the opinionated style is the whole pitch. If you want Mermaid-style diagrams, this is the wrong tool.
Wewrite is a Claude Code skill that handles trending topic research, topic selection, article writing, SEO optimization, and publishing. Built for the Chinese content market. The pipeline goes from identifying trending topics on Chinese social platforms to generating articles optimized for WeChat's distribution algorithm. It covers the entire workflow that content teams typically do manually across multiple tools. The catch: Chinese-language tool for a Chinese platform. If you don't publish on WeChat, this is not for you. AI-generated content at scale raises quality questions regardless of platform, and WeChat has its own content policies around automated publishing that you need to understand before running this at volume.
Chromex is a Chrome side-panel extension that connects your browser to OpenAI's Codex through a local native messaging bridge. Summarize pages, work across tabs and screenshots, edit images, transcribe voice, and run browser-control workflows with visible in-page indicators. MIT licensed. Setup is heavier than a typical extension: clone the repo, `npm install && npm run build`, run `install-native-host.mjs`, then load the unpacked extension at `chrome://extensions`. The architecture (Chrome extension to native host to local bridge to codex app-server) keeps your API key local; raw keys aren't stored in extension storage. Pick this if you live in Chrome, already run Codex, and want one assistant that sees the page you're on. Solo: free, you pay only for Codex tokens. Small teams: same. Large teams or non-Codex shops: skip; this is built around Codex specifically. The catch: Codex-only. Switch to Claude or Gemini for your CLI agent and Chromex doesn't follow. The native bridge is only as polished as the project, which is small and early. For a more mature Chrome AI assistant, Sider and Monica have more features and broader model support.