Skill discovery walks node_modules and .git inside a skill on every startup #51080

Description

Opening OpenCode took 13.3s, 10.0s, and 6.6s on three cold starts before the TUI was ready.

Startup spends several seconds in skill discovery because skills/**/SKILL.md is scanned with followSymlinks: true and dot: true, and Bun.Glob.scan has no ignore option. A skill directory that contains node_modules or .git is walked in full on every launch, even though those directories never contain a skill.

On OpenCode 1.18.31, with no plugins, three cold starts in the same project reached booting location services in 13.3s, 10.0s, and 6.6s. On the fastest run the skill scan itself was 2.3s (message=init at 07:52:56.868Z, message=init count=62 at 07:52:59.173Z). ~/.agents/skills/gstack is a full checkout: node_modules is 703MB / 12,732 files and .git is 57MB. A plain find of those two directories takes 0.07s, so the cost is the scanner, not the disk.

~/.claude/skills is a symlink to ~/.agents/skills, so the same tree is scanned twice and each skill is logged as a duplicate.

This is the same class of walk as #27027 and #30337, both closed as not planned. #27027 is about a symlink to an external tree. Here node_modules is a real directory inside the skill, so dropping followSymlinks does not fix it. Bun.Glob.scan also cannot take an ignore list (cwd, absolute, onlyFiles, dot only).

Please skip descending into node_modules, .git, dist, and .cache during discovery, so nested SKILL.md files are still found and those directories are not stat-ed. Deduping by realpath would also stop the symlink from scanning the tree twice.

Plugins

none

OpenCode version

1.18.31

Steps to reproduce

1. Install a skill that is a full project checkout, so ~/.agents/skills/<name>/node_modules and .git exist. gstack does this.
2. Point ~/.claude/skills at ~/.agents/skills (a symlink).
3. From any project, run opencode --log-level INFO.
4. Time from message=init to message=init count=… in ~/.local/share/opencode/log/opencode.log.

Screenshot and/or share link

No screenshot. Timing is from the server log above.

Operating System

macOS 15.7.5 (Apple Silicon)

Terminal

Measured from the server log, not from terminal rendering. The delay happens before the TUI is ready.