Skip to content
Back to search

loadout

See and manage what your coding assistants load — skills, commands, subagents, plugins and MCP servers, with real usage.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/migsilva89--loadout/badge.svg)](/listings/migsilva89--loadout)

HTML

<a href="/listings/migsilva89--loadout"><img src="/api/listings/migsilva89--loadout/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

brew install --cask migsilva89/loadout/loadout

Or download the [latest release](../../releases/latest) — the [website](https://loadout.migsilva.dev) points at the same file — and drag `Loadout.app` into `/Applications`. The disk image is signed and notarised, so it opens without a Gatekeeper warning and without a trip through System Settings.

macOS 15 or later, on Apple silicon or Intel.

Or build it yourself, which needs Xcode:

git clone https://github.com/migsilva89/loadout.git
cd loadout
./Scripts/build-app.sh
open dist/Loadout.app

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 177 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <img src="Resources/logo-light.png#gh-light-mode-only" width="280" alt="Loadout"><img src="Resources/logo-dark.png#gh-dark-mode-only" width="280" alt="Loadout">
  3. </p>
  4. <h1 align="center">Loadout</h1>
  5. <p align="center">
  6. <strong>See and manage what your coding assistants load.</strong><br><br>
  7. Skills, slash commands, subagents, plugins and MCP servers, from every assistant<br>
  8. on the machine — with how often each one actually fires, and an editor for the ones you own.
  9. </p>
  10. <p align="center">
  11. <a href="https://loadout.migsilva.dev"><strong>loadout.migsilva.dev</strong></a> — what it does, guides and download
  12. </p>
  13. <p align="center">
  14. <img src="https://img.shields.io/badge/macOS-15%2B-blue?style=flat-square" alt="macOS 15 or later">
  15. <img src="https://img.shields.io/badge/Swift-6-orange?style=flat-square" alt="Swift 6">
  16. <img src="https://img.shields.io/badge/license-MIT-lightgrey?style=flat-square" alt="MIT license">
  17. <a href="../../releases/latest">
  18. <img src="https://img.shields.io/github/v/release/migsilva89/loadout?style=flat-square" alt="Latest release">
  19. </a>
  20. <a href="https://buymeacoffee.com/migsilva?utm_source=github-loadout">
  21. <img src="https://img.shields.io/badge/Buy%20me%20a%20coffee-%E2%98%95-FFDD00?style=flat-square" alt="Buy me a coffee">
  22. </a>
  23. </p>
  24. https://github.com/user-attachments/assets/40763b70-7607-403e-9eb5-f0b3e07ad3c4
  25. <p align="center">
  26. <img src=".github/assets/loadout-all.gif" width="1000" alt="Browsing the inventory, disabling and re-enabling a skill, switching off one skill out of a plugin, putting a skill on a second assistant, then asking an assistant to rewrite its description and accepting the change inside the document">
  27. </p>
  28. ```bash
  29. brew install --cask migsilva89/loadout/loadout
  30. ```
  31. Or [download the DMG](../../releases/latest) and drag `Loadout.app` into `/Applications`. Signed and notarised; macOS 15 or later.
  32. ## Features
  33. - **A full inventory** — personal and project skills, everything from plugins, slash commands, subagents and MCP servers, across every assistant on the machine — Claude Code, Codex and Antigravity MCP servers side by side, each marked with its owner
  34. - **Real usage** — how many times each thing fired, when it last did, and in how many projects, read from the assistants' own session logs
  35. - **Honest counts** — a history format that cannot prove an activation is marked unsupported, rather than reporting a zero that looks like disuse
  36. - **Project scope** — answers "what does an assistant see if I open this folder?" — and an Everything list that puts yours and every project's side by side, each row saying where it lives, for when the question is "where did I put that one?"
  37. - **A switch on everything** — turn one skill, command, subagent or MCP server off without deleting it, including a single skill out of a 38-item plugin, and Loadout re-applies that choice when the plugin updates
  38. - **Codex plugins** — installed plugins and their skills appear alongside Claude's, with separate controls. Turning off a plugin shows all its skills as off; turning it back on restores your individual choices. Codex's local plugin controls require an installed Codex version that supports its plugin inventory protocol. Workspace-managed plugin switches stay in Codex.
  39. - **An editor** — create skills, commands and subagents, edit and delete them, with syntax highlighting and live validation against the documented limits
  40. - **A conversation, beside the editor** — ask `claude`, `codex`, `opencode` or `agy` to change a skill; it proposes, you accept change by change
  41. - **Out of a repository, into your own** — a skill, command or subagent that lives in a project becomes yours everywhere with one click. It is a copy: the project keeps its own, so nobody else loses anything at their next pull
  42. - **Help where the question is** — Settings › Help says in plain words what switching something off does to your files, where Loadout keeps its own, and reports a bug with the version and system already filled in
  43. - **A backup before every write** — if the copy fails, nothing is written. Deleting goes to the Trash, never `rm`
  44. - **One skill, every assistant** — share a skill across assistants as symlinks to a single copy, so one edit reaches all of them. Switching it off asks which assistants it should return to, and a skill never changes hands behind your back
  45. ## Install
  46. ```bash
  47. brew install --cask migsilva89/loadout/loadout
  48. ```
  49. Or download the [latest release](../../releases/latest) — the [website](https://loadout.migsilva.dev)
  50. points at the same file — and drag `Loadout.app` into `/Applications`. The disk image is signed and
  51. notarised, so it opens without a Gatekeeper warning and without a trip through System Settings.
  52. macOS 15 or later, on Apple silicon or Intel.
  53. Or build it yourself, which needs Xcode:
  54. ```bash
  55. git clone https://github.com/migsilva89/loadout.git
  56. cd loadout
  57. ./Scripts/build-app.sh
  58. open dist/Loadout.app
  59. ```
  60. ## Chat about your setup
  61. Open **Chat** beside **New skill** from any tab. It uses an assistant CLI already installed and
  62. its existing subscription — there is no API key. Choose the assistant and model in the chat panel.
  63. Press **Ask** on a skill to attach it to the current conversation. You can attach several skills
  64. and remove them above the message box. Selecting another row does not change the attachments or
  65. switch conversations. Removing an attachment excludes its files from future messages; earlier
  66. messages stay in the conversation. **New** starts a chat with no attachments, and **History**
  67. includes earlier conversations, including those started before global chat.
  68. The assistant runs in disposable copies of the attached folders. Review each proposed change
  69. in the chat panel with **Accept** or **Reject**, then choose **Save accepted changes**. Only accepted
  70. changes reach their original files, with a backup first. If a file changed elsewhere, review the
  71. updated proposal before saving. Plugin files remain read-only references.
  72. In the **New skill** sheet, **Create and ask** makes the skeleton and hands it to an assistant with
  73. what you typed as the brief, so the description and body come back as proposals.
  74. ## Sharing a skill across assistants
  75. Each assistant reads its skills from `~/.<name>/skills` — `~/.claude/skills`, `~/.codex/skills`,
  76. and so on. Loadout finds them by itself: any such folder that exists is included, and an assistant
  77. installed tomorrow shows up without a code change. Antigravity CLI (`agy`) is the exception it
  78. knows about: it has no folder of its own and reads `~/.gemini/config/skills`, so that is where
  79. Loadout puts its skills.
  80. Clicking an assistant that does not have the skill puts it there. On disk, the folder is promoted
  81. to `~/.agents/skills/<name>` and each assistant gets a symlink to it — one copy, one edit, both
  82. sides always the same. Clicking a lit mark removes only that link, never the one real copy. The
  83. Loadout menu has **Sync all with …** to close the gaps at once.
  84. A skill can also sit in `~/.agents/skills` with no assistant linked to it, for tools that read that
  85. folder directly. It is listed and marked `shared`, with no assistant against it, and you read and
  86. edit it as usual. Loadout does not know what else reads that folder and doesn't claim to, and it
  87. creates a link only when you click an assistant — never by looking, and never through
  88. **Sync all with …**. Switching it off moves it to `~/.agents/skills-off`, where nothing reading
  89. `~/.agents/skills` sees it, and switching it on moves it back. A skill from there always returns to
  90. `~/.agents/skills`, with the links you confirm.
  91. If two assistants have their own, possibly different, copies of the same skill, the app refuses to
  92. merge them on its own and says why.
  93. ## What it touches
  94. | Data | Location | Written by Loadout? |
  95. |---|---|:---:|
  96. | Your skills, commands, subagents and MCP servers | `~/.claude/`, `~/.codex/`, `~/.gemini/config/`, `~/.agents/`, `~/.<assistant>/` | Only when you save, create, delete or share |
  97. | Backups, taken before every write | `~/Library/Application Support/Loadout/backups/` | Yes |
  98. | Usage index, rebuildable | `~/Library/Application Support/Loadout/usage.sqlite` | Yes |
  99. | Working copies for the assistant conversation | `~/Library/Application Support/Loadout/ask-workspaces/` | Yes |
  100. | The assistants' session logs | `~/.claude/projects/`, `~/.codex/sessions/`, `~/.gemini/antigravity-cli/conversations/` | Never — read only |
  101. Loadout keeps its own files out of `~/.claude`: that directory belongs to Claude, and an app that
  102. keeps its database in someone else's folder is a surprise waiting for whoever wipes `.claude` to
  103. fix something.
  104. The app itself makes no network calls. The assistant CLI it runs on your behalf talks to its own
  105. provider, with the credentials already on your machine; Loadout never sees them.
  106. The test suite never touches any of this: every test runs against a temporary tree, which is why
  107. `Paths` takes its root by injection.
  108. Codex plugin discovery and configuration edits use its local app-server protocol. Loadout does not
  109. start an AI conversation for these operations. To check this integration with an installed Codex,
  110. run `.build/debug/LoadoutApp --self-check-codex` after building. It creates a temporary marketplace
  111. and tests individual switches, parent restoration, updates, backups and configuration preservation.
  112. ## Security
  113. See [SECURITY.md](SECURITY.md). The areas that matter here: writes outside the expected
  114. directories, command execution driven by file contents, and any path where a backup fails without
  115. stopping the write.
  116. ## Contributing
  117. See [CONTRIBUTING.md](CONTRIBUTING.md) for the scope, how to run the tests, and what a pull
  118. request needs. A feature outside that scope will be declined however well it is written, so open
  119. an issue first. The specification, with the acceptance criteria one by one, is in
  120. [docs/SPEC.md](docs/SPEC.md).
  121. ## Status
  122. A personal project, maintained when it suits. It works and is used every day, but it does not come
  123. with a product's promise of support.
  124. Releases are built by `./Scripts/release.sh`, which refuses to run from a dirty tree, an untagged
  125. commit or a branch other than `main`, and runs the tests before signing anything.
  126. Loadout updates itself. A release publishes three files together — the disk image, an identical
  127. copy named `Loadout-<version>-update.dmg`, and a signed `appcast.xml` that points installed copies
  128. at it. The app only accepts an update signed with the key it was built with. `release.sh` will not
  129. print the publish command unless that signed feed exists.
  130. ## Support the project
  131. Loadout is free and stays free. If it saves you time, you can [buy me a coffee](https://buymeacoffee.com/migsilva?utm_source=github-loadout) — it keeps the next release coming.
  132. ## License
  133. [MIT](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.