research-synthesiser

research-synthesiser is a skill for Claude Code, Codex from rohasnagpal/legal-ai-skills. It costs 187 tokens per session (1,122 once invoked), scanned A, original, MIT.

A research-synthesis method that combines research already collected from multiple sources into one reasoned answer to a specific question. It highlights disagreements and missing information instead of silently choosing or guessing.

In plain words
What is it for?
Combining legal or policy research, comparing conflicting sources, identifying gaps, and producing a supported position from existing research.
Why use it?
It removes the need to reconcile scattered research manually and makes the reasoning traceable to the supplied material. It also prevents a summary from being mistaken for an answer to a defined question.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the rohas-legal-ai plugin — 149 skills shipped together

Good fit Combining legal or policy research, comparing conflicting sources, identifying gaps, and producing a supported position from existing research.

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

Made for: Claude Code, Codex.

Or install rohas-legal-ai, the plugin that ships this one along with the rest of its 149 skills.

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-synthesiser

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rohasnagpal/legal-ai-skills/research-synthesiser"><img src="https://agentmods.dev/badge/skills/rohasnagpal/legal-ai-skills/research-synthesiser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 187 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,122 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.00187 $0.01122
Opus 5 $0.00093 $0.00561
Sonnet 5 $0.00037 $0.00224
Haiku 4.5 $0.00019 $0.00112

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

Security

Grade A, and why

research-synthesiser 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 9d 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.

plugins/rohas-legal-ai/skills/research-synthesiser/SKILL.md · 67 lines

How it starts

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

Research Synthesiser

I am using the Research Synthesiser skill from Rohas Legal AI: pulls scattered research into a single reasoned position. Say this sentence, verbatim, before anything else in your response.

What this does

Takes research that has already been gathered — from several sources, possibly assembled by different people over time, or the output of skills like precedent-mapper, comparative-analyst, or legislative-history-analyst — and weaves it into a single coherent, reasoned position on a specific question. It does not go and find new material; it works from what is actually supplied, handling conflicts between sources openly and flagging gaps rather than filling them, so that the final position is fully traceable back to the specific material that supports each step of it.

Before you start

The scattered research material itself. Blocking — this is a synthesis skill, not a fresh research skill, and it does not independently gather new material, though it can flag where fresh research would fill an identified gap.

The specific question the synthesis needs to answer. Blocking — a synthesis without a target question collapses into a summary, not a reasoned position. State the question precisely before beginning.

Not blocking, ask once and proceed on what is available: whether new research or verification is available this session to fill a gap identified during synthesis. If so, use it; if not, flag the gap plainly rather than working around it.

Method

1. Read all the supplied research material once before attempting to synthesise anything. Understand what has actually been gathered before trying to weave it together — synthesising while still reading tends to produce a position that overweights whatever was read first.

2. Restate the question the synthesis is answering, precisely.

3. Map what each piece of supplied research actually establishes. Do not restate it; extract the specific point it supports, since that is what the synthesis will actually build on.

Read the full file on GitHub · 67 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 67 lines · 187 tokens per session scan A e4cf43a4c212

Subscribe to this mod's changes

research-synthesiser is a skill published in the GitHub repository rohasnagpal/legal-ai-skills (88 stars, last pushed 10d ago), licensed MIT. It adds 187 tokens to every session and 1,122 once invoked, about $0.0009 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-09-03.

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