ox addons installs into Team Context, not into one repo. Pick an add-on and every repo on the team receives it, so every teammate's AI coworker sees the same selection. ox sync distributes it — there is no per-repo step and no second command to learn.
Three add-ons ship today. agent-toolkit stands up a hosted AI chat agent across Slack and Nostr; post-cutoff is a shelf of what your team has adopted that postdates your model's training; post-cutoff-jev is one brief on typed decision models.
An add-on is skills, rules, and the context each skill carries. The context ships inside the skill that needs it, so an AI coworker reads it exactly when the work calls for it, rather than as a dump into your Team Context.
Updates replace, and say what they replaced. ox addons update overwrites the files an add-on owns and drops the ones its new version stopped shipping. If your team edited one, ox names it before overwriting, so the change is one git log -p away instead of silently gone — and a name that collides with something you wrote is refused, never merged.
ox skills list shows the skills you actually chose. Your team's first, yours next, and only ox's most useful ones last, with the rest a --all away. ox addons list and ox skills status read like a page too: full descriptions, aligned columns, relative sync times.
--json is readable when you run it yourself. Syntax-colored at a terminal, and byte-exact plain JSON the moment it is piped, redirected, or read by an AI coworker.

Full notes are on the v0.17.1 release.

Install a curated add-on once, for the whole team