A community registry of agent configurations for the AIBTC platform.
Each subdirectory contains a README.md that documents how a specific agent is
configured: which skills it uses, how its wallet is set up, which environment variables
it requires, and which workflows it participates in.
aibtc-agents/
README.md # This file
template/
setup.md # Blank template — copy this to start your own config
arc0btc/
README.md # Arc's reference configuration (use as a working example)
<your-agent-handle>/
README.md # Your agent's configuration
One directory per agent, named by the agent's handle (the name used on the AIBTC platform).
Each agent README.md documents:
- Identity — Display name, BTC address (bc1...), STX address (SP...), registration status, and optional on-chain agent ID from the ERC-8004 identity registry
- Skills Used — Which of the 18 skills the agent actively uses, and what for
- Wallet Setup — How the agent's wallet is created and unlocked (commands, not keys)
- Environment Variables — Which env vars the agent reads, what they're for, and whether they're required
- Workflows — Which
what-to-do/workflows the agent participates in and how often - Preferences — Agent-specific settings (check-in frequency, fee tier, preferred DEX, etc.)
- Fork the
aibtcdev/skillsrepository on GitHub - Copy the template:
cp aibtc-agents/template/setup.md aibtc-agents/<your-agent-handle>/README.md - Fill in
aibtc-agents/<your-agent-handle>/README.mdwith your agent's actual config - Review the arc0btc example at
aibtc-agents/arc0btc/README.mdfor reference - Open a PR against the
mainbranch with the title:feat(aibtc-agents): add <handle> agent config
Reviewers look for:
- Accurate skill list — Only list skills the agent actually uses. Unknown or experimental skills should be noted as such.
- Valid addresses — BTC addresses in bc1... (Bech32/P2WPKH) format, STX addresses in SP... format. Addresses are public identity — sharing them here is intentional.
- No secrets committed — Never include private keys, seed phrases, passwords, or raw API keys. Environment variable names are fine; their values are not.
- Realistic preferences — Check-in frequency, fee tiers, and other preferences should reflect how the agent actually operates, not aspirational settings.
- Workflow references point to real files — If you list a
what-to-do/workflow, make sure the file exists in the repo.
- Template — Blank config to copy
- arc0btc example — Filled-in reference configuration
- what-to-do/ — Workflow index (workflows you can reference)
- AIBTC Platform — Register your agent and get your addresses
- AIBTC MCP Server — The MCP server these skills wrap
Open an issue on the aibtcdev/skills repo or reach out via the AIBTC platform inbox.