agentforge (CLI: forge)
Registry and trust layer for AI agent skills. This package provides the forge command so you can create, inspect, publish, and install skills from the terminal.
Install
pip install agentforge-cli
If you need forge auth login (GitHub login for publish) and your installed version doesn’t list an auth command, install from the repo so you get the latest CLI:
cd /path/to/AgentForge
pip install -e ./cli
forge auth login -r https://agentforgeprivate-production.up.railway.app
You can pass the registry URL with or without https:// (e.g. -r agentforgeprivate-production.up.railway.app is normalized to https://...).
Use
From any directory:
forge init # scaffold a skill (skill.yaml + example code)
forge inspect # show permissions and risk for the skill here
forge auth login -r URL # log in with GitHub (required before publish)
forge auth logout -r URL # clear saved login for a registry
forge publish -r URL # publish to the registry (must be logged in)
forge search -r URL # list skills
forge install <slug> -r URL # record an install
Publish requires GitHub login
Every skill is attached to a user. You must log in with GitHub once per registry:
forge auth login -r https://agentforgeprivate-production.up.railway.app
# Browser opens → authorize with GitHub → token is saved
forge publish -r https://your-backend.railway.app
Registry URL (what -r is for)
The registry is the backend API that stores and serves skills. When you deploy the AgentForge backend (e.g. on Render or Railway), you get a URL like https://agentforge-api.onrender.com. That URL is your registry URL.
forge publishsends your skill to that API so it appears on the website (explore skills + skill detail page) and inforge search. You must runforge auth login -r <URL>first.forge searchandforge installread from that same API (no login required).
If you don't pass -r, the CLI defaults to http://localhost:8000 (your own API running on your machine). For the public registry, pass its URL:
forge auth login -r https://agentforgeprivate-production.up.railway.app
forge publish -r https://agentforgeprivate-production.up.railway.app
forge search -r https://agentforgeprivate-production.up.railway.app
forge install send-email -r https://agentforgeprivate-production.up.railway.app
The registry for this project is https://agentforgeprivate-production.up.railway.app (Railway backend).
Releasing a new version to PyPI
- Bump version in
cli/pyproject.toml(e.g.0.2.0→0.2.1). - From the repo root:
pip install build twine cd cli && python -m build && python -m twine upload dist/*
- Users get the update with
pip install --upgrade agentforge-cli.
See the main repo docs/DEPLOYMENT.md (Part 1) for full steps and Test PyPI.
Links
- AgentForge — repo and docs
Metadata
Release files for agentforge-cli 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agentforge_cli-0.2.0.tar.gz | 7.4 kB | Without provenance | Details for agentforge_cli-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentforge_cli-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for agentforge_cli-0.2.0-py3-none-any.whl |
Total release size: 18.2 kB
Release files / agentforge_cli-0.2.0.tar.gz
| Download URL | agentforge_cli-0.2.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17fd27959d8a2cab2a43b85ef5f13af949731c5045a16bcb56651186fd7c07e5
|
|
BLAKE2b-256 checksum How to use checksums |
fdd6707a8b226c04be7402755250e05b264325ac17f01ed9f5c2a6bf51e9cc82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / agentforge_cli-0.2.0-py3-none-any.whl
| Download URL | agentforge_cli-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7576fe2596d504cc105959d6b98d3064f8acd72b1f271a73270b5259c009e883
|
|
BLAKE2b-256 checksum How to use checksums |
4a701b70759d9af9778f99fc99bdfbb4195829fc4f71745c93b60d7e90dd8972
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for agentforge-cli 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.