agent-response

agent-response is a skill for Claude Code from metraton/gaia. It costs 22 tokens per session (1,600 once invoked), scanned A, original, MIT.

A skill for reading and presenting the saved handoff record from an agent turn. It lets an orchestrator inspect specific parts of that record or find turns that are still open or ended incorrectly.

In plain words
What is it for?
Use it to inspect selected fields, list dispatched turns, find uncleanly closed turns, and view evidence from a particular specialist agent.
Why use it?
It makes it possible to tell the difference between work that found nothing and work that was never searched, without always loading the entire record. This reduces unnecessary reading and helps find incomplete handoffs.

Skill for Claude Code

Written for Claude Code: SubagentStop hook event.

Part of the gaia plugin — 38 skills, 9 agents, 11 hooks shipped together

Good fit Use it to inspect selected fields, list dispatched turns, find uncleanly closed…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/metraton/gaia/agent-response
Install

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.

Any agent
npx skills add metraton/gaia --skill agent-response
Clone the repo
git clone --depth 1 https://github.com/metraton/gaia

Made for: Claude Code.

Or install gaia, the plugin that ships this one along with the rest of its 38 skills, 9 agents, 11 hooks.

Wrote 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.

agentmods badge for agent-response

README.md
[![agentmods](https://agentmods.dev/badge/skills/metraton/gaia/agent-response.svg)](https://agentmods.dev/skills/metraton/gaia/agent-response)
Your own site
<a href="https://agentmods.dev/skills/metraton/gaia/agent-response"><img src="https://agentmods.dev/badge/skills/metraton/gaia/agent-response.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,600 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.01600
Opus 5 $0.00011 $0.00800
Sonnet 5 $0.00004 $0.00320
Haiku 4.5 $0.00002 $0.00160

Measured 6d ago against content hash 2e9395cc1390, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

agent-response 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 6d 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.

skills/agent-response/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Response — Consumer Branch

The durable contract row is the turn's whole delivery. The final message is the signal that the turn ended and carries no envelope of its own, so there is nothing to reconcile against: what the agent declared and what was persisted are one artifact.

The read is not free, and that is the economics that decides whether it happens at all. contract view --field <dotted.path> prints only that subtree of the envelope (agent_status.agent_state, evidence_report.open_gaps, ...), exiting 0 with the value verbatim when the path exists and 1 when it does not — so "searched and found nothing" and "did not search" are distinguishable without opening anything else. Without that distinction the only choice is between the WHOLE row (expensive) and nothing (free), and free wins every time; the narrow --field read is what makes reading the row cheaper than skipping it. contract list --state DISPATCHED lists turns still open; contract list --cut lists every turn that did not close cleanly, naming the specialist and the lane; contract view --harness-id <agentId>, with the id the dispatch returned, gives that turn's own partial evidence.

Reading order

Phase 0 — triage, always, cheap. Read agent_status.agent_state, then cut_reason, then continues_contract_id, in that order. agent_state routes everything downstream. cut_reason says whether that state is honest: it is stamped at birth and cleared only by a clean finalize, so clean-versus-cut is recorded by design, not inferred. never_finalized means the turn never closed itself; backstop_capture and reaped are the stop hook's forensic cleanup; salvaged_truncation is rebuilt purely from the agent's incremental on-disk draft — which is why incremental writes are what survive a cut. continues_contract_id says whether "empty" means anything: a continuation row is born empty by design (Trap 3), and reading this before judging any field as empty is what keeps that design from reading as a failure. What the row does not hold was never delivered — an open_gaps entry the agent only narrated in its message did not survive the turn; treat the row's silence as the finding it is rather than reading the prose as if it had been persisted.

Read the full file on GitHub · 91 lines

Changes

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.

  1. 6d ago First seen · 91 lines · 22 tokens per session scan A 2e9395cc1390

Subscribe to this mod's changes

agent-response is a skill published in the GitHub repository metraton/gaia (3 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 1,600 once invoked, about $0.0001 per session on Opus 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.