yvgude

10 mods across 1 repository, 3.9k stars between them.

compression-safety

01

yvgude/lean-ctx

Cursor rule Cursor

Cursor rule "compression-safety" from yvgude/lean-ctx, covering compression safety — prevent lean-ctx marker corruption, the problem, rules for all agents, never write compressed content to files and file restoration commands.

not rated 3.9k +9 yesterday A 399 tokens original Apache-2.0

yvgude/lean-ctx

Cursor rule Cursor

Shows lean-ctx (MCP) token metrics for this session at the end of each reply.

not rated 3.9k +9 yesterday A 388 tokens original Apache-2.0

lean-ctx

03

yvgude/lean-ctx

Cursor rule Cursor

Token optimization via lean-ctx Hybrid (Shell Hook + MCP).

not rated 3.9k +9 changed 12d ago A 969 tokens original Apache-2.0

lean-ctx

04

yvgude/lean-ctx

Skill Claude CodeCodex

Pick the right lean-ctx tool for reading, searching, understanding and running code with fewer tokens and fewer round trips. Use when lean-ctx MCP tools (ctx) are available or when a command output, file read or search would be large.

not rated 3.9k +9 changed 12d ago C SkillSpector: warn 55 tokens original Apache-2.0

lean-ctx

05

yvgude/lean-ctx

Skill Claude CodeCodex

Pick the right lean-ctx tool for reading, searching, understanding and running code with fewer tokens and fewer round trips. Use when lean-ctx MCP tools (ctx) are available or when a command output, file read or search would be large.

not rated 3.9k +9 changed 12d ago C SkillSpector: warn 55 tokens original Apache-2.0

lean-ctx-review

06

yvgude/lean-ctx

Skill Claude CodeCodex

Review how the lean-ctx ctx MCP tools performed in the current session and file upstream issues for confirmed problems. Use when the user asks to review/audit lean-ctx tool performance, says "lean-ctx review", asks why ctx tools failed or fell back to native tools, or wants to report a lean-ctx bug.

not rated 3.9k +9 yesterday A SkillSpector: warn 73 tokens original Apache-2.0

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: