AgentToolDrop

60 of 71

Repomix

Packs a repository into one AI-friendly file in XML, Markdown, JSON or plain text

Run with npx

npx repomix@latest

Copied from the project's docs at github.com/yamadashy/repomix

Why you'd want it

Repomix reads a local or remote repository, respects .gitignore and .repomixignore, uses Secretlint to leave out files that match known credential formats, and writes one file with a summary, directory structure and file contents, plus token counts per file. The --compress option uses Tree-sitter to keep key code elements with fewer tokens, and large outputs can be split into parts. It also runs as an MCP server (repomix --mcp) and can generate Claude Agent Skills from a codebase.

Best for

  • Feeding a whole codebase to a chat model
  • Checking token counts before sending context
  • Packing a remote GitHub repo for reference

Use it when

You want to hand an LLM a full or filtered snapshot of a repository in one file, or let an agent pack repos through MCP.

Skip it if

Your coding agent already reads files in your workspace and you have no need for a single packed file. By default the MCP server can read any path the host user can, so use --sandbox with untrusted clients.

Same category or shared tags, by drop score.

  1. Rank 34

    Tests and debugs MCP servers from a web UI, a scriptable CLI or a terminal UI

    • score 60
    • 11.1k stars
    • pushed
    • 2.11.0 on
    • Mixed license

    Run with npx

    npx @modelcontextprotocol/inspector
    Use it when, skip it if, stats for MCP Inspector

    Why you'd want it

    The Inspector is the reference developer tool from the MCP project for testing and debugging servers. One npx package gives you a web client that shows the JSON-RPC exchange as you call tools, a CLI with JSON output for CI, shell pipelines and coding agents, and a terminal UI; all three share the same transports, config files and OAuth state. It also installs mcpdo, an experimental client that keeps one connection open across many commands.

    Best for

    • MCP server authors
    • Smoke-testing MCP servers in CI
    • Letting a coding agent check its own MCP server from the shell

    Use it when

    You are building or debugging an MCP server and want to list and call its tools directly, interactively or from a script.

    Skip it if

    You only use MCP servers and never build one. It needs Node 22.19.0 or newer, and on machines without an OS keychain it stores secrets in an unencrypted file unless you supply a key.

    Stats

    Stars
    11,078
    Last push
    Release
    2.11.0,
    License
    Mixed license
    Pricing
    Open source
    Works with
    Docker
    Drop score
    60 of 100
  2. Rank 8

    Gives coding agents structured processes for spec-driven builds, bug fixes and idea assessment

    • score 82
    • 141k stars
    • pushed
    • v1.2.0 on
    • MIT

    Install with uv and create a project

    uv tool install specify-cli
    specify init my-project --integration copilot
    Use it when, skip it if, stats for Spec Kit

    Why you'd want it

    The specify CLI installs skills or command files for your coding agent, which you then run in chat: constitution once per project, then specify, plan, tasks, implement and converge for each feature. Optional extensions add a bug-fixing flow (assess, fix, test) and an idea assessment flow that ends in a go, clarify or stop decision, with reports saved as Markdown under .specify/. It has integrations for dozens of agents, including GitHub Copilot, Claude Code, Codex CLI, Cursor, Gemini CLI and Zed, and you can customize it with extensions, presets and workflows.

    Best for

    • Teams that want a spec before code
    • Keeping agent work reviewable step by step
    • Using one process across several coding agents

    Use it when

    You want a coding agent to work from a written specification, plan and task list rather than one prompt, with artifacts you review at each step.

    Skip it if

    Your changes are small enough that a single prompt does the job. The CLI needs Python 3.11+ and uv.

    Stats

    Stars
    141,300
    Last push
    Release
    v1.2.0,
    License
    MIT
    Pricing
    Open source
    Works with
    Claude Code, Cursor, Codex, Gemini CLI, Zed, Linux, macOS, Windows
    Drop score
    82 of 100
  3. Rank 48

    Reports token usage and costs for Claude Code, Codex and other coding agent CLIs from local data

    • score 52
    • 19k stars
    • pushed
    • v20.0.33 on
    • MIT

    Run with npx

    npx ccusage@latest
    Use it when, skip it if, stats for ccusage

    Why you'd want it

    ccusage reads the usage data that coding agent CLIs store locally and turns it into daily, weekly, monthly and session reports, with per-model breakdowns and separate cache token counts. One report covers Claude Code, Codex, OpenCode, Gemini CLI, GitHub Copilot CLI and more than a dozen other tools, and there are Claude Code extras such as 5-hour billing window reports and a status line integration. Output is a table or JSON, and an offline mode uses cached pricing data.

    Best for

    • Tracking spend across several coding agents
    • Claude Code users watching 5-hour usage windows
    • Exporting usage as JSON for your own dashboards

    Use it when

    You want to see how many tokens and dollars your coding agent sessions use, by day, model, session or project.

    Skip it if

    You need team-wide spend tracking: it only reads local data on the machine where it runs. Costs are calculated from LiteLLM pricing data, not read from your provider bill.

    Stats

    Stars
    19,007
    Last push
    Release
    v20.0.33,
    License
    MIT
    Pricing
    Open source
    Works with
    Claude Code, Codex, Gemini CLI
    Drop score
    52 of 100

For agents

The same entry, as files an agent can read without scraping this page.

# read one entry
curl -s https://agenttooldrop.com/tools/repomix.md

# list the MCP servers in the catalog
curl -s https://agenttooldrop.com/tools.json \
  | jq -r '.tools[] | select(.category=="mcp-server") | .slug'