Backend engineer in Bangalore. I build .NET infrastructure that stays up, and tools that keep AI coding agents cheap, safe and predictable, for Claude Code, Codex, Gemini CLI, Copilot CLI and Cursor. Powered by filter coffee and a grudge against cache re-writes.
Claude Code, Codex CLI, Gemini CLI, GitHub Copilot CLI and Cursor each have their own hooks, configuration files and quirks. These tools read what each agent actually reads and put every claim to the real binary, at zero tokens.
| Tool | What it does |
|---|---|
| everyhook | Write a hook once, run it in every coding agent: one contract, an adapter per agent, install and uninstall into each agent's configuration, and a bench that puts the hook to the JSON each real agent sends |
| codex-config-doctor | What Codex CLI will actually do with your configuration: every layer and the merged result with the source of each key, the AGENTS.md files against their 32 KiB cap, rules, hooks, MCP servers and the Windows sandbox, linted and checked against the real binary |
| agent-windows-doctor | On Windows: which shell Claude Code, Codex CLI, Gemini CLI, Copilot CLI and Cursor each give the model and why, every binary and launcher with the one that runs first, how hooks run on each, the Codex sandbox and the machine settings behind the common issues, proved against the real binaries |
Nineteen small, open-source tools that make Claude Code cheaper, safer and easier to share. No dependencies, few or no tokens, one plugin marketplace, and an end-to-end test that installs all nineteen from GitHub on Windows, macOS and Linux. Website.
| Tool | What it does |
|---|---|
| claude-code-handover | Short sessions that pick up where the last one stopped: a handover file, a decisions log and automatic recall |
| claude-code-team-sync | Share sessions, notes and team context with coworkers through git, synced in the background |
| claude-code-glow | 14 themes for the whole interface, a status line with a context meter, and a live HUD |
| claude-code-guardrails | Stops rm -rf /, force pushes, secrets in commits and .env edits, at zero tokens per allowed call |
| claude-code-notify | A ping when Claude needs you or finishes: terminal, desktop, phone, Slack, Discord or Teams |
| claude-cost-guard | Daily and weekly budgets with zero-token warnings and an optional hard stop |
| claude-md-doctor | What your CLAUDE.md costs in every session, and the fixes that save the most |
| claude-code-starter-kits | A lean, safe .claude/ for .NET, Node, Python, Go, Flutter or Java in one command |
| claude-session-replay | Search every past session, and export one as a self-contained HTML replay |
| claude-chat-ferry | Continue a Cursor or Antigravity chat in Claude Code, or hand a Claude Code session to them |
| claude-session-tidy | Delete, keep and restore your sessions before the 30-day cleanup removes them |
| claude-permission-doctor | See why a permission prompt appeared, drop dead rules and add the ones you keep approving by hand |
| claude-hook-bench | Run every hook with the exact JSON Claude Code sends, and see whether it blocks, allows, adds context or fails |
| claude-relocate | Move Claude Code's config folder to another drive or the XDG folders, with CLAUDE_CONFIG_DIR set for every shell and an undo |
| claude-settings-doctor | A commented settings.jsonc that builds settings.json, the merged settings with their source, and a lint that finds what Claude Code ignores in silence |
| claude-automode-doctor | What auto mode and its classifier decided, read from your transcripts, which refusals were the service rather than your settings, and a lint of the autoMode settings |
| claude-mcp-check | Every MCP server Claude Code would load and from which file, started the way Claude Code starts it, with what its tools cost in context |
| claude-sandbox-doctor | Whether Claude Code's Bash sandbox can work on your machine, why a command ran inside it or outside it, and the sandbox settings that never take effect |
| claude-windows-doctor | On Windows: which shell the Bash tool gets and why, every claude on the machine, and the setup problems behind common Windows issues |
Set them up in one click: this opens a local setup page with the recommended tools already switched on.
npx -y github:nrzz/claude-code-toolkitIt started with an audit of five weeks of my own usage (1,840 requests): 61% of the cost was cache re-writes, and 42 of the 55 full re-writes happened because I came back to an old chat after a break of 55 minutes or more. claude-code-handover fixes that, and its audit scripts let you run the same numbers on your own sessions.
Ideas for the next tool are welcome in the toolkit discussions; follow to see releases land.
Self-hosted observability platform for logs, metrics, traces, alerts and incidents. One deployment instead of five tools: a .NET 10 API and workers, ClickHouse for telemetry, PostgreSQL for metadata, live log streaming, alert rules, incident timelines and a React UI.
One messaging API for .NET that runs on RabbitMQ, Kafka, Redis Streams, Azure Service Bus, AWS SQS, Google Pub/Sub or NATS JetStream, so switching brokers does not mean rewriting business logic. CloudEvents envelope, transactional outbox, idempotent inbox, retries and sagas. MIT licensed, broker adapters in beta.
| Project | What it is |
|---|---|
| pulsedeck | Desktop widget dashboard for Windows and Linux: system vitals, network, markets, news and more |
| open-torrent | Free, ad-free BitTorrent client for Android, Windows and Linux (libtorrent + Flutter) |
| finagent | Self-hosted AI finance agent for stocks, mutual funds, F&O and crypto, paper trading by default |
| web3-portfolio-hub | Web3 portfolio dashboard with multi-wallet tracking (Go + React) |
Sentinel and EventMesh are at the stage where outside eyes change the most: a bug report from a real deployment, a broker EventMesh does not cover yet, a dashboard Sentinel should ship by default.
- Run self-hosted observability or event-driven .NET services? Tell me what is missing in Sentinel discussions or EventMesh discussions.
- Use a coding agent? Every repo has issues labelled good first issue, and ideas for new tools are welcome in toolkit discussions. I would also like to hear what your handover audit numbers look like: share them here.
- Want to contribute? Start with a repo's contributing guide and roadmap, then open an issue so we can scope it together.
- Found a project useful? A star helps other people find it, and following keeps you posted on releases.
C# · .NET · TypeScript · Python · Go · Dart / Flutter · PostgreSQL · ClickHouse · Docker · Kubernetes · and whatever the next bug demands
- GitHub: @nrzz
- Email: nareshprabu18@gmail.com
- Location: Bangalore, India
- Open to collaboration, and available for work on .NET backends, observability and messaging.
Breaking things on my machine so they don't break on yours.