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 instructions/abilityai/trinity/agents-mdgit 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.02588 | $0.02588 |
| Opus 5 | $0.01294 | $0.01294 |
| Sonnet 5 | $0.00518 | $0.00518 |
| Haiku 4.5 | $0.00259 | $0.00259 |
Grade A, and why
trinity AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Stand up a new Trinity instance | [Stand up an instance](#stand-up-a-trinity-instance) | `curl /health` → `{"status": "healthy"}` | How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trinity — Guide for AI Agents
Trinity is an autonomous agent orchestration platform: every agent runs in its own Docker container with scheduling, observability, credential injection, channel integrations (Slack/Telegram/WhatsApp), and a tamper-evident audit trail — self-hosted on infrastructure the operator controls. Agents are plain Claude Code (or Gemini CLI) projects; Trinity is where they run in production.
Detailed documentation index: docs/user-docs/README.md — guides, agent management, credentials, automation, operations, integrations, and the full API reference live there.
Using this file
This is the authoritative entry point for AI agents. If you are an autonomous agent that just landed in this repository or connected to a Trinity instance, start here. The other root files serve different readers — README.md is for humans evaluating Trinity; CLAUDE.md is the contributor working agreement (Rules of Engagement, SDLC, architectural invariants) that Claude Code auto-loads when you edit this codebase. Read CLAUDE.md only when your task is "contribute code"; for everything else, this file is the map.
How to traverse it: find your task in Route by task → jump to that section → run the commands → stop at the Done when signal. Each task is zero-to-value: the shortest path from landing to a confirmed useful result, ending in one check you can run to prove you got there. If a step is ambiguous or a link is dead, that is a bug — report it on the issue tracker.
Route by task
| Your task | Go to | Done when |
|---|---|---|
| Deploy yourself (or another agent) to a Trinity instance | Deploy an agent | trinity agents list (or GET /api/agents) shows the agent running |
| Stand up a new Trinity instance | Stand up an instance | curl /health → {"status": "healthy"} |
| Operate an existing instance (chat, schedules, fleet ops) | Operate over MCP | an MCP tool call (e.g. list_agents) returns results over your API key |
| Evaluate Trinity / summarize it for your operator | README.md, then docs/user-docs/README.md; system design: docs/memory/architecture.md | you can state what Trinity is, how to run it, and its license |
| Contribute to Trinity's codebase | Work on this repository — Claude Code also auto-loads CLAUDE.md | tests pass and a PR is open against dev |
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 · 151 lines · 2,588 tokens per session scan A e444c62d9cf3
trinity AGENTS.md is an instructions file published in the GitHub repository Abilityai/trinity (496 stars, last pushed 4d ago), licensed Apache-2.0. It adds 2,588 tokens to every session, about $0.0129 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.