Share agents and caps

Toolang lets you share agents and caps through remote sources, so others can use them directly or adapt them to their own needs.

Use shared agents

Run a shared agent directly from GitHub or an HTTP(S) URL:

too gh:briceyan/gus chat
too https://toolang.ai/lex.too chat

To create a local copy that you can customize:

too clone gh:briceyan/gus eve

Running a remote source creates a visiting agent, while cloning creates a resident agent.

Use shared caps

Add a shared cap to an existing agent:

too eve skill add gh:briceyan/review

Or reference it directly in a .too program:

with skill gh:briceyan/review

See Extend agents with caps for managing caps.

Publish agents and caps

To share through GitHub using short refs such as gh:OWNER/reviewer, create a public repository named agents under your account:

agents/
├── reviewer.too
├── skills/review/SKILL.md
├── psyches/concise.md
├── services/github.md
└── prompts/summarize.md

Skills are directories containing SKILL.md; other caps are Markdown files.

Once published, others can reference your agent or caps using gh:OWNER/NAME. Sources must be publicly accessible without authentication.

You can also share an agent by hosting its .too file at a publicly accessible HTTP(S) URL.

Declare dependencies

Remote .too files do not automatically include caps from the same repository. Declare required caps explicitly:

with psyche gh:briceyan/concise
with skill gh:briceyan/review
 
agic review:
  Review {{_}} and report actionable findings.

Keep credentials out of published files. See Service file formats for service configuration.

Pin source versions

Use full GitHub refs to specify a repository, path, and revision:

too github://OWNER/agents/reviewer.too@v1.0.0 chat
too eve skill add github://OWNER/agents/skills/review@v1.0.0

Revisions can be tags, branches, or commits. Use commit hashes when exact reproducibility matters.

See Source refs for supported formats and resolution rules.