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 skills add gaia-research/gaia-skill-heaven --skill gaia-issue-resolvergit clone --depth 1 https://github.com/gaia-research/gaia-skill-heavenWrote 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-issue-resolver)<a href="https://agentmods.dev/skills/gaia-research/gaia-skill-heaven/gaia-issue-resolver"><img src="https://agentmods.dev/badge/skills/gaia-research/gaia-skill-heaven/gaia-issue-resolver/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-issue-resolver"><img src="https://agentmods.dev/badge/skills/gaia-research/gaia-skill-heaven/gaia-issue-resolver.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.00174 | $0.02609 |
| Opus 5.5 | $0.00070 | $0.01044 |
| Sonnet 5.5 | $0.00035 | $0.00522 |
| Haiku 4.5 | $0.00017 | $0.00261 |
Grade A, and why
gaia-issue-resolver 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gaia-issue-resolver
Execute the complete resolution pipeline on one already-triaged Gaia issue, selected
by priority (P0–P4) or assignee. Adapted from favorchurch/rock-steward's
rock-issue-resolver; the six-phase shape and the Kill Criteria discipline are its
contribution, the Gaia mechanics below are this repo's.
Prerequisite: the issue is triaged — it has a priority label, a size, and a stated
problem. If it doesn't, stop and run /gaia-triage on it first. This skill resolves; it
does not decide what is worth resolving.
1. Non-negotiables
- Zero follow-up debt. Do not close an issue by filing a trailing "clean up" issue
that carries its own unfinished work. Everything a reasonable reviewer would call a
direct consequence of this change belongs in this change. This is
gaia-skill-tree's sprint-completeness rule applied at issue granularity: genuinely new, out-of-scope work discovered along the way may still be filed; the issue's own remainder may not. - Kill Criteria before code. Every acceptance requirement is written as an explicit
KC-1 … KC-Nlist, posted as a comment on the issue before implementation starts, and checked off from evidence before closing. An issue with no Kill Criteria has no definition of done. - Draft PR first, push often. Branch, then open a draft PR as the first git operation after the first commit — before the work is finished. Push after each phase. Draft PRs stay draft until a human marks them ready.
- Programmatic-first. Registry mutations go through
gaia devverbs, never hand-edits toregistry/nodes/orregistry/named/frontmatter. If the right verb does not exist, file it as aCLI+tech-debtissue and say so in the PR — do not work around it. - Read-only during audit. Phase 2 observes and never mutates. No
gaia devwrite verb, nogit push, no site regeneration, until the plan is posted. - Class A / Class B dual delivery, where it applies. If the issue describes a
recurring drift rather than a one-off defect, ship a detector alongside the fix:
- Class A — a read-only, deterministic check that observes the condition
(
founder/steward/POLICY.yamldeclares the Class A repairs Gaia Steward runs unattended;scripts/verify_evidence.pyandscripts/verify_lockstep.pyare the shape to copy). - Class B — an operational routine,
--dry-runby default with an explicit--applygate, living infounder/steward/routines/. A one-off typo fix does not need either. A fourth recurrence of the same drift does.
- Class A — a read-only, deterministic check that observes the condition
(
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 · 204 lines · 174 tokens per session scan A 121d10ff446b
gaia-issue-resolver is a skill published in the GitHub repository gaia-research/gaia-skill-heaven (4 stars, last pushed 3d ago), licensed MIT. It adds 174 tokens to every session and 2,609 once invoked, about $0.0007 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
architecture-compass
Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use…
review-refiner
Facilitate a structured conversation to customize how the review molecule works -- atom loading rules, severity classification, report format, scope rules, insight capture, and health logging. Produces a formal review-standards.md document that the review molecule will use as its process configuration. Use when the…
review
Perform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when…
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…
backlog
Seed a backlog from the project's documents: the Product Owner reads docs/ (plus the constitution and ROADMAP.md), proposes an ordered list of feature-sized items each traced to a source section, the user edits the list, and on explicit confirmation each item is filed as a GitHub issue that /story-time can import. Use…
pocket-closing
Close a reviewed Pocket phase or plan when the user explicitly requests closeout, including as part of an end-to-end request. Reconcile verdicts with log.json, advance only a passing phase, append a readable per-phase closeout, and finalize the plan when all phases are done. A passing verdict alone does not authorize…