Community templates: shipping reusable agents
A good agent template is a prompt, a cap, and a tool list — frozen, named, and one click from running.
Most teams rebuild the same agents: triage, summarize, draft, extract. Templates turn that repetition into a library. A submission includes a system prompt, a model strategy, a spend cap, and a tool list — the exact configuration that makes the agent reproducible.
Why the cap travels with the template
A prompt without a cap is a footgun. A template that ships without a spend cap assumes the operator will set one, and operators forget. We make the cap part of the template so a one-click deploy lands already-governed.
Two-stage review
Submissions land as TemplateSubmission records with a pending status. Admins review the prompt, validate the tool surface, and promote approved submissions to AgentTemplate records that appear in the public library. The review step is small but non-negotiable — it is the difference between a library and a marketplace.
The result: an operator who needs a triage agent no longer writes one. They click, deploy, and the agent is on governed rails in seconds.