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 OpenHands/extensions --skill research-briefgit clone --depth 1 https://github.com/OpenHands/extensionsWrote 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/openhands/extensions/research-brief)<a href="https://agentmods.dev/skills/openhands/extensions/research-brief"><img src="https://agentmods.dev/badge/skills/openhands/extensions/research-brief/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/openhands/extensions/research-brief"><img src="https://agentmods.dev/badge/skills/openhands/extensions/research-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 80 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00040 | $0.00838 |
| Opus 5.5 | $0.00016 | $0.00335 |
| Sonnet 5.5 | $0.00008 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
research-brief scanned grade A with 1 finding 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 14d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \ How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Brief Writer Automation
Set up a recurring automation that researches a topic and publishes a brief to Notion.
Prerequisites
Required integrations
Both MCP integrations must be installed in Settings → MCP:
- Tavily MCP — for web research and source gathering
- Notion MCP — to publish the research brief
Information to collect
Ask the user for:
- Topic — what should be researched (e.g. "AI code review tools", "competitor pricing changes")
- Keywords and competitors — specific terms, companies, or products to track
- Source quality rules — any preferences on source types (e.g. prefer academic papers, exclude social media)
- Cadence — how often should the brief run? (daily, weekly, bi-weekly)
- Notion destination — which Notion database or page should receive the brief
- Citation style — inline links, footnotes, or a references section
- Brief structure — default: Executive Summary, Key Findings, Implications, Recommended Actions, Sources
Setup Workflow
Step 1 — Verify MCP access
Test each integration:
Use the Tavily MCP to search for a sample topic.
Use the Notion MCP to search for the destination database.
If any fail, tell the user which integration needs to be installed first.
Step 2 — Configure the schedule
Based on the user's cadence preference, build a cron schedule:
- Daily:
0 8 * * 1-5(weekday mornings) - Weekly:
0 9 * * 1(Monday morning) - Bi-weekly:
0 9 1,15 * *(1st and 15th)
Ask for timezone preference.
Step 3 — Build the research prompt
Construct a prompt that includes:
- Research topic and keywords
- Competitor/entity tracking list
- Source quality preferences
- Brief structure template
- Notion destination details
- Citation format
Step 4 — Create the automation
Set OPENHANDS_HOST and AUTH_HEADER for the request below:
- OpenHands Cloud or Enterprise - a
<HOST>value is in your system prompt: use it asOPENHANDS_HOST, withAUTH_HEADER="Authorization: Bearer $OPENHANDS_API_KEY" - Local Agent Canvas - an Automation backend is listed in
<RUNTIME_SERVICES>: use itsurl_from_agentasOPENHANDS_HOST, withAUTH_HEADER="X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY"
What ships with it
5 files 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.
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.
- 14d ago Changed 56d718a1d6c6
- 1mo ago First seen · 102 lines · 40 tokens per session scan A 662a6bf42ec9
research-brief is a skill published in the GitHub repository OpenHands/extensions (167 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 838 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…