Skip to main content
agentgg agents manages the agents a scan can use: the official catalog and any agent a user adds.

​
Subcommands

list shows a category summary instead of the full table once more than 30 agents match and no filter is set. Pass --all to force the full table.
SCOPE shows scoped when the agent’s where sets extensions or filePatterns, and all when it reviews every file. add and remove only touch the custom directory. remove never searches the official catalog, so it reports a clear error for a built-in slug and never deletes the wrong file. install pins the catalog to one exact point in the repository, so it can move backward as well as forward: agentgg agents install 0.1.28. The next agentgg agents update moves you to the latest release again.

​
Contribute an agent to the catalog

The official catalog lives at agentgg-agents on GitHub.
  1. Fork the repository and branch from main.
  2. Add or edit a .md file under the right category folder. The filename must match the slug field.
  3. Test the agent against a fixture: agentgg scan ./test-code -t ./agents/category/my-check.md.
  4. Run agentgg agents lint . from the repository root. A pre-commit hook runs the same check.
  5. Open a pull request. The template asks for a description and test evidence.
  6. A maintainer reviews the prompt quality, the false-positive risk, and the category placement.
Pull requests are squash-merged. Set author to your GitHub handle so it ships with the agent file: agentgg agents info <slug> and the raw file show it. A scan report names the agent by its slug, not its author. To select the agent in a scan afterward, see Choose agents.