krishnashakula

Toollens — Development skill for Claude Code

Development community

Give your agent 2,468 tools.

How to install Toollens

This entry records only its repository, not the path inside it, so there is no exact command to give. Open krishnashakula/toollens and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Toollens does

Give your agent 2,468 tools. It sees 3. A Rust MCP gateway: dependency-aware tool discovery, policy-checked execution, measured on 110 real vendor MCP servers (26/28 tasks at half the cost of Anthropic's tool search).

Alternatives in Development

Bypass 403 — Probe a 403/401 endpoint with the most-paid bypass tricks (header injection, path encoding, method swap, WAF f 4.5k ★
Claudes C Compiler — Claude Opus 4.6 wrote a dependency-free C compiler in Rust, with backends targeting x86 (64- and 32-bit), ARM 2.6k ★
Gov Backlinks — Free .gov backlinks - drive the user's browser through SAM.gov, the SBA small business listing, and state vend 195 ★

README

🔍 ToolLens

Give your agent 2,468 tools. It sees 3.

**An MCP gateway in Rust. Put any number of MCP servers behind it: your agent discovers, inspects and calls exactly the tools it needs, and finding a tool never grants permission to run it.**

[![CI](https://github.com/krishnashakula/toollens/actions/workflows/ci.yml/badge.svg)](https://github.com/krishnashakula/toollens/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE) [![Rust 1.89+](https://img.shields.io/badge/rust-1.89%2B-orange)](https://www.rust-lang.org/) [![MCP](https://img.shields.io/badge/MCP-gateway-7c3aed)](https://modelcontextprotocol.io/) [![PRs welcome](https://img.shields.io/badge/PRs-welcome-blue)](CONTRIBUTING.md)

Claude answers through ToolLens with 5 of 2,468 tools in view; the same request with every tool exposed is rejected by the API at 1.43M tokens; then the benchmark results

Real run, not a mock-up: Claude Opus 5.5 against 110 vendor-published MCP servers. Full 4K/60 fps video in the v0.1.0 release.

MCP clients send **every tool definition with every request**. Connect enough servers and that stops working: the 110 real vendor servers in this repo's benchmark expose 2,453 tool definitions, which come to **1.43M tokens per request, and the API rejects every call** before the model runs. Below that limit you still pay for, and distract the model with, hundreds of tools it will never use.

ToolLens sits between the agent and your servers and shows the agent three tools instead:

Tool	What it does
`discover_tools(goal, limit?)`	Up to 10 tool ids for a goal: direct matches plus the tools they depend on, each with the reason it is there
`inspect_tool(tool_id)`	Full input/output schema, server provenance, and the current policy decision
`i