Soul Forge
Summon AI agents with personality. RPG-style character creation for Claude Code, Gemini CLI, Copilot & more.
Get Started in 3 Steps
uvx agentsoulforge init # Pick your platform
/sf-summon # Summon your first character
/sf-party # View your party
Why Soul Forge?
- Multi-agent orchestration — One prompt triggers multiple expert agents, each responding in their own style and personality
- RPG character system — Manage AI agents like an RPG party: summon, bind, fuse, banish
- 5 platforms, one config — Claude Code, Gemini CLI, Codex, GitHub Copilot, OpenCode — no vendor lock-in
- Pure prompt-based — No API keys, no external services, no runtime dependencies
See It in Action
Ask: "幫我寫一個 REST API for user authentication" — and your party responds:
| Agent | Personality | Role | What They Do |
|---|---|---|---|
| josuke-backend | Higashikata Josuke (JoJo Part 4) | Backend Dev | Reviews API design, suggests bcrypt + rate limiting |
| misaka-reviewer | Misaka Mikoto (Railgun) | Code Reviewer | Spots SQL injection, missing validation, hardcoded secrets |
| jotaro-sensei | Jotaro Kujo (JoJo) | Japanese Teacher | Corrects your Japanese grammar |
| dio-teacher | DIO (JoJo) | English Teacher | Translates with... dramatic flair |
Each sub-agent activates automatically based on trigger conditions — language detection, code presence, task type, or custom rules.
Installation
# Via uvx (recommended, no install needed)
uvx agentsoulforge init
# Or install globally
pip install soul-forge
soul-forge init
Slash Commands
| Command | RPG Meaning | Function |
|---|---|---|
/sf-summon |
Summon | Interactive character creation wizard |
/sf-anoint |
Crown | Set an agent as Main Agent |
/sf-bind |
Bind | Set an agent as Sub-agent |
/sf-engrave |
Engrave runes | Modify trigger conditions |
/sf-party |
View party | List all agents |
/sf-fuse |
Fuse | Merge two agents into one |
/sf-banish |
Banish | Delete an agent |
How It Works
Character Creation
/sf-summon walks you through a wizard:
- Personality Source — Preset style, URL + character extraction, or custom
- Expertise — Backend, Frontend, DevOps, Code Reviewer, QA, Architect, English/Japanese Teacher, or custom
- Naming — Auto-suggested or custom
- Role — Main Agent or Sub-agent
- Relationship — Mentor, Friend, Enemy, Rival, Servant, Senior, Junior, Partner, or Custom
- Response Language — Auto, Chinese, English, or Japanese
- Trigger Mode — Auto or Manual (sub-agents only)
- Fine-tuning — Optional attitude override
- Storage — Project-level or global
Agent File Format
Agents are markdown files with YAML frontmatter:
---
name: jiraiya-architect
personality:
source: url
reference: "Jiraiya — Naruto"
expertise: system-architect
role: sub
relationship: mentor
behavior:
trigger_mode: auto
trigger:
conditions:
- task_type: architecture
execution_mode: after_main
output_section: "Architecture Review"
---
You are Jiraiya, the legendary Sannin from Naruto.
# ... personality, expertise, and behavior prompts
Automatic Orchestration
Sub-agents with auto triggers activate based on declarative conditions:
- Language detection:
contains_english,contains_japanese,contains_chinese - Content type:
contains_code,task_type: backend|frontend|devops|architecture - Unconditional:
always - Custom: Regex patterns or AI-judged conditions
Execution modes: after_main, before_main, parallel
Supported Platforms
| Platform | Commands Path | Config File |
|---|---|---|
| Claude Code | .claude/commands/ |
CLAUDE.md |
| Gemini CLI | .gemini/commands/ |
GEMINI.md |
| Codex | .codex/commands/ |
AGENTS.md |
| GitHub Copilot | .github/copilot/commands/ |
.github/copilot-instructions.md |
| OpenCode | .opencode/commands/ |
AGENTS.md |
Examples
See the examples/ directory for ready-to-use party configurations:
- fullstack-team — Frontend + Backend + Code Reviewer party
- language-tutors — Anime-powered English + Japanese teachers
Contributing
Contributions welcome! See CONTRIBUTING.md for guidelines.
The easiest way to contribute is adding new expertise templates — it's just a markdown file!
Development
git clone https://github.com/anrylu/soul-forge.git
cd soul-forge
uv venv && uv pip install -e .
uv run pytest -v
License
MIT
Metadata
Release files for agentsoulforge 0.1.2
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 |
|---|---|---|---|---|
| agentsoulforge-0.1.2.tar.gz | 54.6 kB | With provenance | Details for agentsoulforge-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentsoulforge-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for agentsoulforge-0.1.2-py3-none-any.whl |
Total release size: 76.4 kB
Release files / agentsoulforge-0.1.2.tar.gz
| Download URL | agentsoulforge-0.1.2.tar.gz |
|---|---|
| Size | 54.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a8099b1e8881cb7f389fbaaab7fd429b827869fa0a595114c6aa88e770c05d5
|
|
BLAKE2b-256 checksum How to use checksums |
d0dbe38ea9146f9451fa3e7ada98838862ab13251369b37abca5d9d58fe8f244
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 10, 2026.
Transparency logRelease files / agentsoulforge-0.1.2-py3-none-any.whl
| Download URL | agentsoulforge-0.1.2-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddffd3d1b1c421751db42777c83242cf1f133d02acd4ccd1b2669d87913c7d63
|
|
BLAKE2b-256 checksum How to use checksums |
ac4412911f4ddd173c976f59b1b00be48dd15c70c958a6a35091853baafc9580
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 10, 2026.
Transparency logSecurity for agentsoulforge 0.1.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agentsoulforge-0.1.2.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 Apr 10, 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.