Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add metraton/gaia/plugin install 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/skills/metraton/gaia/gaia-research)<a href="https://agentmods.dev/skills/metraton/gaia/gaia-research"><img src="https://agentmods.dev/badge/skills/metraton/gaia/gaia-research/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/skills/metraton/gaia/gaia-research"><img src="https://agentmods.dev/badge/skills/metraton/gaia/gaia-research.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.00000 | $0.02401 |
| Opus 5 | $0.00000 | $0.01201 |
| Sonnet 5 | $0.00000 | $0.00480 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
gaia-research 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 11d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gaia Research
Mining a repository for ideas Gaia can actually use, by reading what its code does rather than what its authors say it does.
Core principle
A repo's description is not evidence. The user already read it -- that is why the repo is bookmarked at all. Summarizing it back hands them their own input with someone else's signature on it, and because it arrives shaped like analysis it is worse than returning nothing: it consumes the credit that real analysis would have earned. The evidence is the code, read where the mechanism is actually implemented.
The counterpart is the expensive half: reading code produces HYPOTHESES; running it produces FACTS. A claim about behavior that rests only on reading is not established. It is plausible -- and a well-written plausible claim is indistinguishable from an established one to everyone downstream, which is exactly why it has to be marked rather than trusted.
Where this sits, and where it stops
This runs on user request, and its output feeds the conversation from which a
brief (brief-spec) and then a plan may later be born. It stops at digested
ideas: it produces neither briefs nor plans. If you are writing acceptance
criteria, decomposing tasks, or ordering an implementation, you have left this
skill and should hand back. The stop is hard because a brief commits someone to
build, and nothing this stage emits has yet earned that commitment.
The rule that orders everything: the claim type sets the burden of proof
Every idea answers what it contributes, and each possible answer carries a different, non-negotiable burden.
| The idea claims | What must be established before it is delivered |
|---|---|
| It IMPROVES something Gaia already has | Corroborate by executing how that existing Gaia thing behaves today. Without that execution the idea is not delivered -- or is delivered explicitly marked unverified. |
| It is a NEW SKILL | Confirm Gaia does not already have it: gaia/skills/ and the index in skills/README.md. |
| It is a NEW COMPONENT or capability | Confirm it does not exist, and name the surface it would live in -- gaia/agents/, gaia/skills/, gaia/hooks/modules/, gaia/bin/cli/. |
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.
- 11d ago First seen · 183 lines · 0 tokens per session scan A eef75ed8e494
gaia-research is a skill published in the GitHub repository metraton/gaia (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,401 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-31.
Other skills, from other repositories
review-team
A multi-reviewer code review process that checks a change from several specialist viewpoints and combines the results into one report. It can cover bugs, security, tests, dependencies, frontend behavior, and continuous-integration workflows.
ultra
Fans the work out as a fleet of parallel Grok and Codex agents billed to their own subscriptions, then synthesizes one result. The peer engine equivalent of ultracode, adding intensity without spending Claude quota on the fleet. Use it for genuinely broad goals, not only explicit asks for intensity.
grok-prompting
Brief writing guidance for composing self contained Grok briefs for coding, review, diagnosis, and second opinion tasks.
smoke
Runs a three probe live smoke wave after a plugin update and reports gate chain health before real work rides it.
codex-result-handling
Internal contract for returning Codex companion output without alteration.
shipwrights-loop
Drive multiple Jira tickets sequentially through the /shipwrights-epic pipeline. Auto-picks the next ticket, watches the PR until merged, transitions Jira to shipped, repeats. Resumable across Claude Code sessions via .shipwrights/loop-state.json. Invoked as /shipwrights-loop [N] | --status | --abort.