Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gaia-research/gaia-skill-heavennpx agentmods add skills/gaia-research/gaia-skill-heaven/gaia-triageWrote 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/gaia-research/gaia-skill-heaven/gaia-triage)<a href="https://agentmods.dev/skills/gaia-research/gaia-skill-heaven/gaia-triage"><img src="https://agentmods.dev/badge/skills/gaia-research/gaia-skill-heaven/gaia-triage/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/gaia-research/gaia-skill-heaven/gaia-triage"><img src="https://agentmods.dev/badge/skills/gaia-research/gaia-skill-heaven/gaia-triage.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.00221 | $0.03327 |
| Opus 5.5 | $0.00088 | $0.01331 |
| Sonnet 5.5 | $0.00044 | $0.00665 |
| Haiku 4.5 | $0.00022 | $0.00333 |
Grade A, and why
gaia-triage 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 1mo 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gaia-triage
Triage has three workstreams — GitHub issue hygiene, skill-batch intake review, and the cross-repo prioritization sweep. Run them independently or together depending on what the user asks for. All three produce documented, auditable decisions rather than silent changes.
This skill absorbed favorchurch/rock-steward's rock-triage (2026-09-01): its impact
sizing, priority matrix, four-step inspection, and prioritized-matrix output landed here
as Workstream 3 rather than shipping as a second, competing triage skill. There is one
gaia-triage. Its priority ladder is the P0-P4 ladder /gaia-meta-audit and
/gaia-meta-sweep already use — one vocabulary, not two.
Triage is not cartography. Sorting a backlog of known work is this skill; planning an
effort too big for one session as a map of decision tickets is /wayfinder. Taking one
triaged issue end-to-end to a PR is /gaia-issue-resolver.
Headquarters
Every issue lives on gaia-research/gaia-skill-tree, regardless of which repo the fix
lands in. One tracker for the whole org.
export GAIA_HQ=gaia-research/gaia-skill-tree
Tag the target repo on the issue when the work lands elsewhere — a line at the top of the
body, **Target repo:** \gaia-research/gaia-skill-heaven`, matching the /wayfinderconvention. Cross-repo references use the fullgaia-research/#form; a bare#` always resolves to HQ.
Classification taxonomy
Every triaged issue gets a size and a priority. Both are labels; neither is invented ad hoc (see label hygiene below).
Impact size
Blast radius, structural complexity, and data footprint — not hours.
| Size | Means |
|---|---|
XS |
Trivial fix, label correction, single config value, negligible blast radius |
S |
Minor scoped adjustment, one predicate, isolated UI touch-up |
M |
Standard scoped task — one command, one schema field, one localized workflow |
L |
Cross-component change, non-trivial data backfill, multi-surface impact |
XL |
Architecture-level refactor, substantial registry debt remediation |
XXL |
High blast radius — core schema, authorization, or site-wide parity |
Epic |
Umbrella spanning multiple distinct sub-issues across domains |
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.
- 1mo ago First seen · 309 lines · 221 tokens per session scan A c802bd2ceaa6
gaia-triage is a skill published in the GitHub repository gaia-research/gaia-skill-heaven (4 stars, last pushed today), licensed MIT. It adds 221 tokens to every session and 3,327 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
requirement-forge-refiner
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution…
tasks
Turn an approved SPEC.md into a complete TASKS.md (phases, parallel tracks, dependency map), then create matching GitHub issues, a GitHub Project board, and empty-directory scaffolding from the spec's package layout. Use whenever the user invokes /ank:tasks, says "break this into tasks", "create the issues", "wire up…
agency-os
Notion-as-source-of-truth dispatch board. Status flow Suggestion→Discussion→To-Do→In Progress→Done with subtasks, recurring tasks, deps, batch agent execution. Trigger: 'suggest X', 'discuss X', 'approve', 'start X', 'run todo', 'mark X done', 'kill X', 'next', 'capture this to Notion', 'agency-os status'.
product-manager
Use when writing user stories or acceptance criteria, defining product requirements, prioritising a feature backlog, creating a product roadmap, analysing product metrics, facilitating discovery for a new feature, evaluating trade-offs between product directions, or any task that requires deciding what to build and…
project-manager
Use when planning sprints, tracking delivery milestones, managing dependencies, identifying risks, writing status reports, running retrospectives, or coordinating cross-functional execution of a defined scope. Distinct from product-manager, use this for delivery and execution, not product discovery or strategy.
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…