ForgeCat profile for compound-engineering-plugin

[seulch]

Hi Every team,

I’m working on ForgeCat, a tool for making agent profiles such as skills, agents, rules, commands, hooks, and MCP configs easier to install across different agent tools.

We found the compound-engineering plugin useful as a broad set of agent workflows for review, research, design, and shipping, so we created an initial ForgeCat profile for it here:

Profile repo: https://github.com/nota-america/forgecat-agent-profiles/tree/main/profiles/everyinc/compound-engineering-plugin

Install example:

forgecat install @forgecat/everyinc_compound-engineering-plugin

ForgeCat currently supports Claude Code, Cursor, and Codex, and we’re also planning support for OpenClaw, Hermes, and other agent runtimes. The goal is to help people reuse useful agent workflows across tools while keeping attribution and links back to the original repository.

I wanted to check with you before we continue maintaining this profile.

Which option best matches your preference?

1. The current ForgeCat profile is okay as-is.
2. Keeping the profile is okay, but some description, attribution, license, or supported platform notes should be corrected.
3. You’d prefer to publish or maintain the ForgeCat profile directly.
4. You’d prefer that we remove this ForgeCat profile.

If you prefer removal, we can take it down.

Getting Started:

npm install -g forgecat
forgecat search <keyword>
forgecat install @forgecat/everyinc_compound-engineering-plugin

Docs: https://forgecat.ai/docs

Thanks, and happy to adjust anything that doesn’t represent the original project accurately.

[tmchow]

@seulch Please refresh your data about the plugin. We are only skills, not formal agent definitions anymore since the latest release which was a significant refactor. Also, we service all major coding agents, so at least mention Codex ifyou are mentioning Cursor and Claude Code in tags.

You can also get author info etc for attribution from any of the plugin.json in the repo.

Ok for you to maintain and host for now but if we were to host it, what would that look like in the repo? Do you have like a .forgecat directory support you expect that hosts the profile?

[seulch]

Hi @tmchow, thanks for taking a look and for the detailed notes.

You’re right. I updated the ForgeCat profile to match the current version of this repo, and updated the supported platform notes to include Codex as well.

Just to clarify the repo/hosting model: the forgecat-agent-profiles repo is a public catalog of profiles that we package and publish under @forgecat in the ForgeCat registry. The for-forgecat directory is the ForgeCat-packaged version of this repository’s agent/skill configuration.

For this profile, we keep attribution back to the original project in the package metadata and README, including the original repository link, license, author/source information, original commit, and the original README content.

If you’d prefer to maintain the ForgeCat profile directly, that works too. You can publish it under your own ForgeCat scope, and we can unpublish the @forgecat/everyinc_compound-engineering-plugin version once yours is available.

No need for any .forgecat support addition on your side; we support scanning the repo as a whole and converting it into a "ForgeCat Profile" inside of our CLI.

The repo is just a catalog of public profiles uploaded in ForgeCat's registry, so once you decide to publish and maintain the compound-engineering profile yourself, we can change the metadata of the profile on our repo to match it.

If you choose to publish/maintain directly, the current publish flow is roughly:

npm install -g forgecat
forgecat login

git clone https://github.com/EveryInc/compound-engineering-plugin
cd compound-engineering-plugin

forgecat init --scope <your-forgecat-username> --description "<your description>"
forgecat scan --track
forgecat validate
forgecat push --visibility public

Thanks again!