file-finder
Skill0 starsChanged 8 months agoMITView on GitHub
Find files matching a name pattern in a directory. Use when the user wants to locate files by name, extension, or wildcard pattern.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- yanggujun/open-axletheir own version, first seen Sep 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- yanggujun/open-axle★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- disk-usageSkill
- file-backupSkill
- json-formatterSkill
- slug-generatorSkill
- text-case-converterSkill
- text-searchSkill
- word-countSkill
The file
Files
File Finder / 파일 찾기
Find files matching a name pattern in a directory. 디렉토리에서 이름 패턴과 일치하는 파일을 찾습니다.
Usage / 사용법
bash run.sh <PATTERN> [DIRECTORY]Arguments / 인수:
| # | Name | Description | 설명 |
| 1 | PATTERN | Filename pattern with wildcards (e.g. *.txt) | 와일드카드를 포함한 파일명 패턴 (예: *.txt) |
| 2 | DIRECTORY | Directory to search in (default: current) | 검색할 디렉토리 (기본값: 현재 디렉토리) |
Example / 예시
bash run.sh "*.log" /var/logOutput / 출력:
PATTERN: *.log
DIRECTORY: /var/log
---
/var/log/syslog.log
/var/log/auth.log
---
FOUND: 2
STATUS: OKSuccess / Failure — 성공 / 실패
- Success / 성공: File list with
FOUND:count andSTATUS: OK(exit code 0) — 파일 목록,FOUND:수,STATUS: OK(종료 코드 0) - Failure / 실패:
ERROR:message (exit code non-zero) —ERROR:메시지 (종료 코드 0이 아님)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.