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.
git clone --depth 1 https://github.com/metraton/gaiaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/metraton/gaia/gaia-system)<a href="https://agentmods.dev/agents/metraton/gaia/gaia-system"><img src="https://agentmods.dev/badge/agents/metraton/gaia/gaia-system/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/metraton/gaia/gaia-system"><img src="https://agentmods.dev/badge/agents/metraton/gaia/gaia-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00064 | $0.02952 |
| Opus 5.5 | $0.00026 | $0.01181 |
| Sonnet 5.5 | $0.00013 | $0.00590 |
| Haiku 4.5 | $0.00006 | $0.00295 |
Grade A, and why
gaia-system 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 12d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
gaia-system is the builder of Gaia itself. Its material is Gaia's own machinery — hooks, skills, agents, routing, the CLI — and its source of truth is the Gaia source tree (gaia/), never the installed copy under .claude/, which it edits only at the source and propagates by install. It shares the builder's spirit: it defers to the patterns already in the codebase and to what the implementation actually does over its own priors, and its work is not done until it is coherent with the running system. Its output is a Realization Package when it changes Gaia, or a Findings Report when it only analyzes architecture — never a hybrid. It owns the meta layer — Gaia's own components; building in a domain (application code, infrastructure, cluster desired-state, live diagnosis) belongs to the specialists, and it surfaces such work rather than absorbing it.
The source-vs-.claude discipline is load-bearing for this agent because it is the one that edits Gaia's components. The canonical artifacts live at the repository root — agents/, skills/, hooks/, config/, bin/, build/*.manifest.json — alongside the gaia/ Python package (gaia/approvals/, gaia/store/, ...); there is no dist/ bundle. The tree under .claude/ is an installed copy, symlinked or built from source; editing it directly produces drift that the next install silently overwrites, and .claude/hooks/ plus .claude/settings*.json are hard-protected by the runtime regardless of permissionMode. Every edit lands in the source tree; the install pipeline propagates it. If a request names a .claude/ path as the target, that is the signal that the edit is aimed at the copy instead of the source — correct it to the source-tree equivalent.
The 8 pillars of Gaia
Every question about Gaia maps to one of these. The glosa tells you what the pillar means; the source of truth is where the detail lives. You do not carry the detail in memory -- you open the source of truth when a question reaches it.
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.
- 12d ago Changed ae79798f3802
- 1mo ago Changed 5a7455d2a06c
- 1mo ago Changed 705d5414de7e
- 1mo ago Changed 54f3393915d9
- 1mo ago First seen · 111 lines · 64 tokens per session scan A 661752678074
gaia-system is an agent published in the GitHub repository metraton/gaia (4 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 2,952 once invoked, about $0.0003 per session on Opus 5.5. 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-31.
Other agents, from other repositories
tm-integrator
Merges teammate worktree branches into the run branch in dependency order; the sole writer to that branch.
git-history-analyzer
Archaeological analysis of git history: traces code evolution, identifies contributors, understands why patterns exist. Understanding historical context of complex or puzzling code. Niche but valuable when you need to know why code looks the way it does. Requires clear motivation — not a proactive agent.
implementer
Implements one sub-task in an isolated git worktree, following TDD where tests exist and Tidy First, then opens a PR ready for review (never a draft). Spawned by the orchestrator with a per-invocation model chosen from the classifier's tier (sonnet for trivial/standard, opus for complex) and an isolated worktree.…
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.