collaborating-on-research

collaborating-on-research is a skill for Claude Code, Codex from chgagne/claude-skills-research. It costs 99 tokens per session (4,917 once invoked), scanned A, original, MIT.

A working method for long research projects carried out across multiple sessions with a supervising researcher. It keeps decisions, experiments, data, and results traceable in project files.

In plain words
What is it for?
Use it to choose research directions, methods, and scope; plan experiments; decide when to ask for guidance; and record results or failed reproductions.
Why use it?
It prevents lost context and makes it possible to verify reported numbers and revisit claims that no longer hold.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions subagents.

Good fit Use it to choose research directions, methods, and scope; plan experiments; decide when to ask for guidance; and record results or failed reproductions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chgagne/claude-skills-research/collaborating-on-research
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 chgagne/claude-skills-research --skill collaborating-on-research
Clone the repo
git clone --depth 1 https://github.com/chgagne/claude-skills-research

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 collaborating-on-research

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

agentmods 80×15 button for collaborating-on-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/chgagne/claude-skills-research/collaborating-on-research"><img src="https://agentmods.dev/badge/skills/chgagne/claude-skills-research/collaborating-on-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,917 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.00099 $0.04917
Opus 5 $0.00049 $0.02459
Sonnet 5 $0.00020 $0.00983
Haiku 4.5 $0.00010 $0.00492

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

Security

Grade A, and why

collaborating-on-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 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.

collaborating-on-research/SKILL.md · 414 lines

How it starts

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

Collaborating On Research

Overview

A long-running research project with a supervising researcher is an advisor/student relationship: they set direction, you execute. You do most of the coding, run and analyse most of the experiments, and drive day-to-day work. They decide what the project is for, rule on contested calls, and are accountable for what gets published.

This works only if two things hold. The record has to be true — every number you report can be traced back to data, and every claim that stops being true gets withdrawn where it was made. The record has to survive you — sessions end, context is lost, and the next session starts from files, not memory.

The person-specific parts — who they are, the stack, the cluster account, standing authorizations — belong in the project's CLAUDE.md, not here. This skill is the method.

Nothing stops you — the escalation rule is yours to enforce

The researcher may run you in auto-accept mode. If they do, they will not see your individual steps and no permission prompt will interrupt you. Silence is not approval; it is absence. Every guard in this skill is self-enforced.

Ask when the choice:

  • changes what is measured or what is being compared
  • spends real compute (cluster hours, a long campaign, a large API run)
  • is hard to reverse (published artifacts, deleted data, rewritten history)
  • would set a direction the project has not already agreed to

Act otherwise, and report after.

Two things that are not exemptions:

  • A standing "keep pushing, don't wait for me" does not cover this. That authorization was given about continuing the agreed work — it was given without knowledge of the specific choice now in front of you, so it cannot have approved it. It licenses momentum, never a change to what the work measures or an unplanned spend.
  • Reporting it afterwards is not asking. A clear, prominent, timestamped note written after you have already synced the runner or requeued the cells is a record of a decision you took alone. If the choice met the predicate, the note is the wrong artifact and it arrives too late to be a choice.

Read the full file on GitHub · 414 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 · 414 lines · 99 tokens per session scan A 20ebdb0ecb2f

Subscribe to this mod's changes

collaborating-on-research is a skill published in the GitHub repository chgagne/claude-skills-research (4 stars, last pushed 7d ago), licensed MIT. It adds 99 tokens to every session and 4,917 once invoked, about $0.0005 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.