The repository or configuration that created this release differ from a previous release. View details.
role-forge
Canonical role-definition toolkit for coding agents.
role-forge keeps one canonical role source and renders it into platform-specific agent formats for tools like Claude Code, OpenCode, Cursor, and Windsurf.
Install
uv tool install role-forge
Quick start
role-forge add PFCCLab/precision-agents -y
role-forge add ./local-roles
role-forge render --target claude
role-forge list
add and update ask before overwriting existing files. Use --yes to skip confirmations.
Project installs are the default. Use role-forge add -g, role-forge list -g, and
role-forge remove -g for the user scope in ~/.agents/roles. Rendering merges both
scopes and lets project roles override same-id user roles.
Why this repo exists
- avoid maintaining the same role prompt in multiple tool-specific formats
- keep capabilities, delegation policy, and model tiers in one canonical source
- validate hierarchy and output layout before rendering
- support extension through adapter entry points
Capability model
Canonical roles declare abstract capabilities such as basic, read, write, web-access, delegate, bash, safe-bash, and all. role-forge expands those once into a shared intermediate capability model, then each adapter renders the matching tools and permissions for its target. If a role omits capabilities entirely, basic is applied by default.
Documentation
- live site:
https://role-forge.sixbones.dev - docs home:
docs/index.md - canonical role format:
docs/reference/canonical-role-definition.md - CLI reference:
docs/reference/cli.md - configuration:
docs/reference/configuration.md - adapters:
docs/reference/adapters.md - architecture:
docs/architecture/system-overview.md - development:
docs/development/contributing.md - deployment:
docs/development/deployment.md
Documentation site
This repo now includes a Zensical doc set inspired by the structure used in volvox.
uv add --dev zensical
zensical serve
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for role-forge 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| role_forge-0.1.3.tar.gz | 85.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| role_forge-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 116.5 kB
Release files / role_forge-0.1.3.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | role_forge-0.1.3.tar.gz |
|---|---|
| Size | 85.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34ca555900fc73c37f79788803cbb3dafa361fac08fd0064da17c81ec59131a5
|
|
BLAKE2b-256 checksum How to use checksums |
209e311959df723019300c343c9bfb1dc8c44518fe2cd02631b9d18d2ee1cb37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 20, 2026.
Transparency logRelease files / role_forge-0.1.3-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | role_forge-0.1.3-py3-none-any.whl |
|---|---|
| Size | 31.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e5c9a9fc31c1e78d93597829b2273a69a76216797b7af39d8de89a274e71f62a
|
|
BLAKE2b-256 checksum How to use checksums |
f582c56b562144b8a24e56b0e76f9520bdc489da5c68438fdea534f98fcce0dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 20, 2026.
Transparency logSecurity for role-forge 0.1.3
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.
Change of provenance
The configuration that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Attestation for role_forge-0.1.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 20, 2026.
Transparency logA 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.
