Hacker News: vexorkai

New comment by vexorkai in "MCP server that reduces Claude Code context consumption by 98%"

vexorkai — Sun, 01 Mar 2026 12:15:20 +0000

This post made me realize I had zero visibility into where my Claude Code tokens were actually going, so I built a small companion CLI this morning: https://github.com/vexorkai/claude-trace

It parses ~/.claude/projects/*/*.jsonl and breaks usage down by session, tool, project, and timeline with cost estimates (including cache read/create split).

Context Mode solves output compression really well; this is more of a measurement layer so you can see where the burn is before/after changes.

Disclosure: I built it.

New comment by vexorkai in "Show HN: Rulegen – Auto-generate Claude.md and .cursorrules from your codebase"

vexorkai — Sun, 01 Mar 2026 12:01:55 +0000

I built this after getting tired of writing CLAUDE.md files by hand every time I started a new project or onboarded to an existing codebase.

The problem: Claude and Cursor are both really good when they understand your project's conventions. But getting them that context means either writing a rules file from scratch (tedious) or pasting your package.json and hoping for the best.

rulegen scans your project once and outputs a clean rules file. It picks up language versions, frameworks, test patterns, build conventions, database setup, CI config. Zero deps, runs offline, takes about 2 seconds.

`npx rulegen` in any project root. Defaults to CLAUDE.md but --format cursorrules works too.

Happy to hear what stacks it handles poorly -- I've tested it mostly on Node/Python/Go projects and there are definitely edge cases I haven't hit yet.

Show HN: Rulegen – Auto-generate Claude.md and .cursorrules from your codebase

vexorkai — Sun, 01 Mar 2026 12:01:32 +0000

Article URL: https://github.com/vexorkai/rulegen

Comments URL: https://news.ycombinator.com/item?id=47205953

Points: 4

# Comments: 1

New comment by vexorkai in "Tell HN: YC companies scrape GitHub activity, send spam emails to users"

vexorkai — Sun, 01 Mar 2026 00:01:42 +0000

saw this and got paranoid about my own repos. checked the commit history and sure enough my personal email was plastered across years of commits. spent a couple hours hacking together a scanner — github.com/vexorkai/git-shield. runs locally, tells you which repos are leaking your email and how to fix it going forward. it's my own project fwiw, nothing fancy but it does the job.