Agent Extensions Manager banner
oliwier-xiao oliwier-xiao

Agent Extensions Manager

Development community

Description

One list for the skills, plugins and MCP servers behind Claude Code, OpenCode and Codex. Turn any of them on or off, set one up for a project, pull its upstream, and copy the command that invokes it. An Omarchy bar widget.

Installation

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

README

Agent Extensions

An Omarchy bar widget for the skills, plugins and MCP servers behind your coding agents.

Three agents, three sets of config files, three ideas of where a skill lives. Claude Code keeps skills in `~/.claude/skills`, plugins in a marketplace cache, and its connectors nowhere on disk at all. OpenCode keeps skills in `~/.config/opencode/skills`, plugins as npm specifiers in `opencode.json`, and lets a plugin inject MCP servers at runtime that never appear in any list. Codex keeps its own again. Some of it is the same skill, symlinked into two places, and no view anywhere shows you that.

This widget is that view. One searchable list of everything all three agents can load, grouped by what the thing is for, with what each one costs you in tokens on every single turn, which agent can see it, and the command that invokes it — on your clipboard, in the spelling that particular agent expects.

What it shows you

Three of these are true on the machine this was written on, and no other tool reports any of them.

**The same skill loaded twice, differing.** `omarchy` exists as a real directory under `~/.claude/skills` and as a symlink to `/usr/share/omarchy` under `~/.codex/skills`. The two files are not the same. Claude Code and OpenCode read one, Codex reads the other, and nothing says so. Deduplicating on path alone calls them unrelated; on name alone, identical. Both are wrong, so the list deduplicates on the resolved path and then compares content hashes.

Differing content is not on its own a fault, so the declared version decides which it is. Impeccable ships one release compiled per harness on purpose -- the build for each agent carries anti-pattern rules aimed at that model's habits -- and two of those sitting side by side, both declaring 4.1.1 and thirty-four files apart, is the careful thing to do rather than a mistake. That is reported quietly, as "also built for another agent". A copy declaring a different version is behind, which is drift an