quangdang46

Fast File Search — AI skill for Claude Code

AI community

Ultra-fast file search toolkit for AI agents, Neovim, and code editors.

How to install Fast File Search

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

What Fast File Search does

Ultra-fast file search toolkit for AI agents, Neovim, and code editors. MCP server for Claude Code/Cursor/Codex, frecency-ranked search, symbol indexing via tree-sitter, and a Rust core that outperforms ripgrep and fzf in long-running processes.

Alternatives in AI

Jcodemunch MCP — Cut AI token costs 95%+ on code exploration 2.6k ★
Rust Skills — Rust Developer AI Assistance System — Meta-Problem-Driven Knowledge Indexing 893 ★
Cc Mini — Ultra-light Harness scaffolding for AI agents, a mini version of claude code 825 ★

README

ffs — Fast File Search

ffs — code-aware file search CLI for humans and AI agents

![Release](https://img.shields.io/github/v/release/quangdang46/fast_file_search?logo=github&label=release) ![CI](https://img.shields.io/github/actions/workflow/status/quangdang46/fast_file_search/ci.yml?branch=main&logo=github&label=CI) ![License](https://img.shields.io/badge/License-MIT-green.svg) ![Rust](https://img.shields.io/badge/Rust-stable-blue?logo=rust)

**A code-aware file search CLI for humans and AI agents. Really fast.** Replaces `find` + `grep` + `glob` + `cat` + tree-sitter with one binary. Typo-tolerant fuzzy matching, frecency ranking, token-budget reader, MCP server.

curl -fsSL "https://raw.githubusercontent.com/quangdang46/fast_file_search/main/install.sh?$(date +%s)" | bash

🤖 Agent Quickstart (MCP / Robot Mode)

ffs ships a 15-tool MCP server over stdio. The installer auto-configures it for Claude Code, Codex, Cursor, Windsurf, Gemini, OpenCode, and more.

# Run as MCP server
ffs mcp

# Agent-friendly JSON queries
ffs grep 'fn main' --format json
ffs symbol FilePicker --format json
ffs read crates/ffs-engine/src/lib.rs --budget 5000 --format json
ffs map --depth 3 --format json
ffs overview --format json
ffs deps path/to/file.rs --format json

**Output conventions**

stdout = structured data (JSON or text)
stderr = diagnostics, warnings
exit 0 = success

**MCP tools exposed:** `ffs_find`, `ffs_grep`, `ffs_multi_grep`, `ffs_symbol`, `ffs_callers`, `ffs_callees`, `ffs_refs`, `ffs_flow`, `ffs_impact`, `ffs_outline`, `ffs_siblings`, `ffs_deps`, `ffs_map`, `ffs_overview`, `ffs_read`

TL;DR

The Problem

File search and code navigation require a menagerie of tools: `find`, `fd`, `grep`, `rg`, `glob`, `cat`, plus a tree-sitter plugin for symbol queries. Each has different synt