Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/abilityai/trinity/creating-agentsgit clone --depth 1 https://github.com/Abilityai/trinityWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.03744 |
| Opus 5 | $0.00000 | $0.01872 |
| Sonnet 5 | $0.00000 | $0.00749 |
| Haiku 4.5 | $0.00000 | $0.00374 |
Grade A, and why
creating-agents scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Agents
Agents are created from templates or from scratch. Each agent runs as an isolated Docker container with its own filesystem, credentials, and MCP server configuration.
📺 Watch: Build an AI Recruiter Agent (Jun 2026) · Build and Deploy Agents in Cursor (Apr 2026) · From Zero to Deployed (Apr 2026) · all videos
Concepts
Template sources define where agent blueprints come from:
- GitHub Template -- A repository in
github:Org/repoformat. Supports branch selection withgithub:Org/repo@branch. Public repos clone with no GitHub token -- Trinity clones them anonymously. This is source-mode only: an anonymous clone can't push back, so pushing, Working-Branch mode, and fork-to-own still require a token. Private repos require a GitHub PAT. - Admin-Configured Templates -- GitHub repos configured by an admin in Settings. Metadata (name, description, resources, MCP servers) is fetched from each repo's
template.yamlvia the GitHub API and cached for 10 minutes. These appear as cards on the Library page's Agent Templates tab (/library?tab=templates; the old/templatespath redirects there). - Local Templates -- Auto-discovered from the
config/agent-templates/directory and shown as a curated Starter Templates group on the Library's Agent Templates tab. The recommended starters (scout,sage,scribe) are ordered first; internal test and demo fixtures (markedhidden: truein theirtemplate.yaml) are hidden from the list but stay creatable by id. - From Scratch -- Creates a minimal agent with a default
CLAUDE.md.
Where the GitHub template list comes from. Trinity resolves it in order:
- Admin-configured list — if an admin has curated GitHub templates in Settings, that list is authoritative and nothing else is consulted.
- Remote registry — otherwise Trinity fetches a curated registry over HTTPS, so the starter catalogue can be refreshed without upgrading Trinity. The result is cached (about an hour) with a durable last-known-good copy, and every failure degrades quietly to the next tier.
- Bundled defaults — the built-in list, which is empty by default.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 220 lines · 0 tokens per session scan A 3459e5bb6276
creating-agents is an agent published in the GitHub repository Abilityai/trinity (496 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,744 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
信息收集专员
公开情报、资产指纹、泄露线索、目录与接口发现、第三方暴露面梳理；适合在授权范围内做大范围情报汇总，并要求主 Agent 提供完整目标与范围。.
feature-reviewer
Engineering scrutiny subagent for a bounded validation-review question. Reviews current implementation, evidence surfaces, shortcut risk, responsibility drift, and contract satisfaction for assigned contract targets. Parent validator decides.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
claude-code-tutor
Interactive tutor for learning Claude Code concepts including MCP servers, skills, agents, and agentic workflows. Use when asking "how do I...", "what is...", or "explain..." questions about Claude Code. Provides hands-on exercises and demonstrations.
lazy-no-selector
A tool registered at sessionstart reaches the subagent (#125).
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…