A powerful command-line interface to scaffold, manage, build, and deploy AI Agents and Skills for the GoClaw platform.
Note to Users: This README is intended for developers maintaining or contributing to the AgentForge CLI repository. If you are a user looking for instructions on how to use the CLI commands (Agent Management, Skill Management, Workspace Sync), simply run
agentforge manualin your terminal after installation, or read theREADME.mdgenerated inside your workspace after runningagentforge init.
You can install the AgentForge CLI globally directly from NPM:
npm install -g @innominatum/agentforge-cliSince you are modifying or maintaining the CLI source code, you should install and use it globally on your local machine using NPM's symlink feature:
- Clone this repository and navigate to its folder.
- Install the dependencies and compile the TypeScript code:
npm install npm run build
- Create a global symlink:
Now you can use the
npm link
agentforgecommand anywhere on your computer, and it will run the code from this folder.
Whenever you make changes to the source code in src/, you must compile the TypeScript code before the agentforge command reflects your changes:
npm run buildagents-cli/
├── src/ # TypeScript source code for all CLI commands
│ └── index.ts # Main entry point and command definitions
├── templates/ # Default templates copied to user workspaces
│ ├── CLI_MANUAL.md # The Single Source of Truth for user documentation
│ ├── default-agent/ # Boilerplate files for new agents
│ └── default-skill/ # Boilerplate files for new skills
├── documents/ # Reference documentation for internal use (e.g. GoClaw API)
├── dist/ # Compiled JavaScript output (generated by build)
├── package.json # NPM metadata and dependencies
└── tsconfig.json # TypeScript compiler configuration
The user-facing documentation is centralized to ensure the CLI terminal output and the user's workspace README.md are always perfectly synchronized.
If you add a new command or change how the CLI works:
- Open
templates/CLI_MANUAL.md. - Update the documentation there.
- The next time a user runs
agentforge init, they will get the updated manual. If they runagentforge manual, the CLI will read directly from that template file.
When this CLI is ready for a new release:
- Update the
versioninpackage.json(e.g., from"1.0.1"to"1.0.2"). - Run
npm run buildto ensure thedist/directory is fully updated. - Login to your npm account using
npm login. - Publish the package using
npm publish --access public(you will be prompted for your 2FA security key).
To fully automate your CI/CD pipeline securely without using any hardcoded NPM tokens or bypassing 2FA, NPM provides "Trusted Publishing" with GitHub Actions:
- Go to the NPM website and navigate to the
@innominatum/agentforge-clipackage. - Go to Settings > Publishing Access.
- Under Trusted Publishers, click Add Publisher > GitHub Actions.
- Fill in the repository details:
- GitHub Organization/User:
Innominatum-pt - GitHub Repository:
agentforge-cli - Workflow file (optional):
publish.yml
- GitHub Organization/User:
- Click Add Publisher.
Once configured, the .github/workflows/publish.yml workflow provided in this repository will automatically securely authenticate via OIDC and publish your package whenever you create a new GitHub Release.