Radar Topics Builders Weekly Reads

Open Source Radar

0xwilliamortiz/

ratchet

Your agent reads the rules. This checks whether it followed them.

430stars

+624h

85forks

1issues

MITlicense

2026since

Star historydaily snapshots by VibeCrowd

Alternatives & relatedmatched by topic overlap

DietrichGebert/

Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.

96k5.3kJavaScriptnew

thedotmack/

Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More

90k7.8kJavaScript

affaan-m/

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

238k36kJavaScript

Graphify-Labs/

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

102k9.9kPython

rtk-ai/

CLI proxy that reduces LLM token consumption by 60-90% on common dev commands. Single Rust binary, zero dependencies

75k4.7kRust

ComposioHQ/

awesome-claude-skills

A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows

72k8.1kPython

Compareratchet vs ponytail ratchet vs claude-mem ratchet vs ECC

Agent skills inside · 3

ratchet-reviewReviews a diff or a whole repository for over-engineering only, and returns a delete list rather than prose. Finds reinvented standard library calls, dependencies the platform already covers, abstractions with one implementation, wrappers that only forward, configuration nothing reads and dead flexibility. Use whenever the user says "review for over-engineering", "what can we delete", "is this over-engineered", "find the bloat", "audit this repo", or invokes /ratchet-review. Pair it with a normal correctness review, it deliberately does not look for bugs.Security ratchetEnforces a measured complexity budget on coding work. Reaches for the standard library, native platform features and code that already exists in the repository before writing anything new, and treats every added dependency, file and line as a cost that has to be justified. A hook measures the real diff and reports overruns back mid-task, so the budget is a number, not a mood. Use this on ANY coding task: writing, refactoring, fixing, reviewing, choosing libraries, or designing an interface. Use it whenever the user says "ratchet", "keep it minimal", "simplest thing that works", "yagni", "don'tDocumentation ratchet-ledgerReports what the ratchet actually measured in this repository: the session ledger at .ratchet/ledger.jsonl, the accepted complexity mark, and every `ratchet:` shortcut comment left in the code with its ceiling and its upgrade trigger. Use when the user says "ratchet ledger", "/ratchet-ledger", "what did we defer", "show the complexity trend", "what shortcuts are in here", or asks whether the codebase is getting simpler or more complex over time. Reports real recorded numbers only, never estimates.Other

SharePost on X LinkedIn

All trending repos Revenue-verified startups →