Making the installation a bit less Claude Code centric

[joachim-isaksson]

Since several tools seem to adopt or already have concepts similar to Claude Code (for example, Copilot CLI has subagents, Gemini CLI has commands, OpenCode has subagents, commands and a skills plugin), maybe it would be time to make the installer a bit less claude code specific. Now we have;

--claude-code-commands [BOOL]
--use-claude-code-subagents [BOOL]
--standards-as-claude-code-skills [BOOL]

...but adding --opencode-commands, --copilot-commands etc. seems a bit redundant, adding pretty much an installer flag or a few per tool instead of having them "by concept". One suggestion would be something like;

--tool [TOOLNAME].      for example --tool claude-code
--install-tool-commands [BOOL]
--install-tool-subagents [BOOL]
--standards-as-tool-skills [BOOL]

...and then have a tools folder in agent-os with scripts that implements the actual installation in the .claude/.opencode/.copilot/.gemini folder with the right format (folder names and header structure on esp. agent files tend to differ slightly)

Good idea/bad idea/...?

[Staxed]

100% excellent idea. Especially for those of us using multiples it would be awesome to have the built in ability to use them all how we want.