research-closure-harness: Skill for Claude Code

.agents/skills/research-handoff/SKILL.md

research-handoff is a skill for Claude Code, Codex from Shiien/research-closure-harness. It costs 166 tokens per session (2,161 once invoked), scanned A, original, MIT.

A workflow for handling research when work is passed between agents or when an agent returns results. It turns transcripts, logs, tables, and claims into evidence, a decision, and a next action.

In plain words
What is it for?
Use it to summarise returned research, interpret experiment results, or prepare a self-contained research task for another coding agent.
Why use it?
It helps prevent research findings from becoming disconnected from the original question or experiment. It also makes handoffs understandable to an agent that cannot see the earlier conversation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions Codex.

This is Shiien/research-closure-harness's own configuration. It tells Claude Code and Codex how to work on research-closure-harness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything research-closure-harness configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python tools/research_closure.py guard.

Reuse

Borrowing it

Nothing to install: this file belongs to Shiien/research-closure-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Shiien/research-closure-harness/main/.agents/skills/research-handoff/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Shiien/research-closure-harness

Made for: Claude Code, Codex.

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 research-handoff

README.md
[![agentmods](https://agentmods.dev/badge/skills/shiien/research-closure-harness/research-handoff/github.svg)](https://agentmods.dev/skills/shiien/research-closure-harness/research-handoff)
Your own site
<a href="https://agentmods.dev/skills/shiien/research-closure-harness/research-handoff"><img src="https://agentmods.dev/badge/skills/shiien/research-closure-harness/research-handoff/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.

agentmods 80×15 button for research-handoff

Your own site · 80×15
<a href="https://agentmods.dev/skills/shiien/research-closure-harness/research-handoff"><img src="https://agentmods.dev/badge/skills/shiien/research-closure-harness/research-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 166 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,161 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00166 $0.02161
Opus 5 $0.00083 $0.01081
Sonnet 5 $0.00033 $0.00432
Haiku 4.5 $0.00017 $0.00216

Measured 12d ago against content hash 71ca855a7554, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

research-handoff 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.

.agents/skills/research-handoff/SKILL.md · 171 lines

How it starts

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

Research Handoff

Scope

Two directions across one boundary — the point where work leaves your context and returns.

  • Inbound: an agent returns logs, tables, and claims. Convert them into evidence, one decision, and one next action.
  • Outbound: a task goes to an agent that cannot see this conversation. Convert the current claim and experiment card into a prompt that stands alone.

The research-closure skill and docs/protocol.md (installed as docs/research_closure_protocol.md in a bootstrapped repository) own the state machine: frozen claim, WIP limits, experiment cards, decision taxonomy, claim-lowering ladder. Reference them rather than restating them.

There is no required output shape. Structure and length follow the input — a twenty-line log gets a five-line synthesis, not a report. What follows are constraints on what must be true of the output, not a template to fill.

Before either direction

Read .research/state.json and the open experiment card, then run:

python tools/research_closure.py guard

Three things are needed: the frozen claim, the open card if there is one, and that card's pre-registered metric and kill criterion. Outside an initialized repository, ask which claim the work is meant to test rather than inferring one — a synthesis anchored to a claim the researcher never froze is worse than no synthesis, because it looks like closure.


Part I — Reading agent output

Keep measurement separate from conclusion

Five kinds of statement, kept distinct whether or not they are explicitly labeled:

  1. Observed — directly measured, with an artifact behind it.
  2. Derived — computed from observed values.
  3. Interpretation — the best current explanation.
  4. Hypothesis — plausible, untested.
  5. Claim boundary — what the evidence does not support.

Agent output routinely blurs 1–3. The characteristic failure is an interpretation inheriting the certainty of the number that suggested it, and a hypothesis becoming a result because it was restated confidently.

Read the full file on GitHub · 171 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. 12d ago First seen · 171 lines · 166 tokens per session scan A 71ca855a7554

Subscribe to this mod's changes

research-handoff is a skill published in the GitHub repository Shiien/research-closure-harness (10 stars, last pushed 19d ago), licensed MIT. It adds 166 tokens to every session and 2,161 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens