add-brain-provider
Skill4 starsChanged 4 months agoMITView on GitHub
Add a BYOK or local brain to ZeroAgent Studio. Use when integrating a new AI API or local inference engine.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Prefer smallest default model
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Brain Provider
Files (in order)
src/engines/<provider>.ts—BrainEngine:name,isAvailable,chatsrc/engines/index.ts—getEngine()switchsrc/types/index.ts—BrainType,ApiKeysif BYOKsrc/lib/brainResolver.ts—isBrainConfigured(),getBrainCostLabel(); fallback copy if BYOKsrc/lib/brainLabels.ts—getBrainDisplayName()src/components/settings/SettingsPanel.tsx— key + models (free options first)src/components/inspector/NodeInspector.tsx— brain + model dropdowntests/engines/<provider>.test.ts— positive, negative, edge (see test-engineer rule)
BYOK pattern
export function createProviderEngine(apiKey: string): BrainEngine {
return {
name: 'Provider',
isAvailable: () => !!apiKey,
async chat(messages, options) { /* fetch provider */ },
}
}Local engine pattern
- Dynamic
import()for heavy deps createModelLoadCallback()for download UIisAvailable()checks WebGPU / browser support- Prefer smallest default model
Prometheus
- Register in free-brain selection if usable without key
- Missing key →
brainResolverfallback, not crash - Settings: label cost clearly (
Free (local),Free tier, etc.)
Validate
npm run ciManual: Demo workflow + agent node on new brain; verify activity log on fallback.
Rules: .cursor/rules/zeroagent-engineer.mdc · .cursor/rules/zeroagent-test-engineer.mdc
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/pre-commit-quality-gate.mdcCursor rule
- .cursor/rules/release-versioning.mdcCursor rule
- .cursor/rules/zeroagent-advisor.mdcCursor rule
- .cursor/rules/zeroagent-debugger.mdcCursor rule
- .cursor/rules/zeroagent-engineer.mdcCursor rule
- .cursor/rules/zeroagent-planner.mdcCursor rule
- .cursor/rules/zeroagent-reviewer.mdcCursor rule
- .cursor/rules/zeroagent-security-auditor.mdcCursor rule
- .cursor/rules/zeroagent-test-engineer.mdcCursor rule
- add-browser-toolSkill
- pre-commit-ciSkill
- release-versioningSkill
- review-before-mergeSkill
- ship-patchSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

