local-research-runner

local-research-runner is a skill for Claude Code, Codex from jbdamask/McBrain. It costs 137 tokens per session (3,276 once invoked), scanned A, original, MIT.

A local research-task runner that takes up to five pending tasks from a JSONL tracker, has research agents work on them, saves the findings as Markdown notes, and marks the tasks complete.

In plain words
What is it for?
Use it to process a local research backlog, run several research tasks in parallel, and save the results into a McBrain knowledge base.
Why use it?
It removes the need to manually start each queued research task and update its status afterward.

Skill for Claude CodeCodex

Part of the mcbrain plugin — 4 skills, 1 command, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/jbdamask/mcbrain/local-research-runner
Any agent
npx skills add jbdamask/McBrain --skill local-research-runner
Clone the repo
git clone --depth 1 https://github.com/jbdamask/McBrain

Made for: Claude Code, Codex.

Or install mcbrain, the plugin that ships this one along with the rest of its 4 skills, 1 command, 1 MCP server.

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 local-research-runner

README.md
[![agentmods](https://agentmods.dev/badge/skills/jbdamask/mcbrain/local-research-runner.svg)](https://agentmods.dev/skills/jbdamask/mcbrain/local-research-runner)
Your own site
<a href="https://agentmods.dev/skills/jbdamask/mcbrain/local-research-runner"><img src="https://agentmods.dev/badge/skills/jbdamask/mcbrain/local-research-runner.svg" alt="Measured on agentmods" height="20"></a>
Per session 137 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,276 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00137 $0.03276
Opus 5 $0.00068 $0.01638
Sonnet 5 $0.00027 $0.00655
Haiku 4.5 $0.00014 $0.00328

Measured 5d ago against content hash 30cea58c1c22, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

local-research-runner 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 5d 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/mcbrain/skills/local-research-runner/SKILL.md · 166 lines

How it starts

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

Local Research Runner

Drain the "To do" queue of a local JSONL research tracker (the kind initialized by the local-research-db skill) by researching each task with a subagent and writing findings as markdown files into the vault's raw/notes/ directory. The standard McBrain ingest flow then picks those files up — there is no special "local-bridged" ingest mode.

Prerequisites

  • The vault must be a McBrain vault — registered in ~/.mcbrain/registry.json (visible via the mcbrain MCP server's list_vaults tool). Every <vault> path in this skill means the absolute path from that registry entry.
  • The vault's CLAUDE.md must have ## Research tracker → Backend: local.
  • The vault must have raw/research_tasks/tasks.jsonl (created by local-research-db).
  • Python 3 must be available on the user's host (for the atomic-write helper). No third-party packages, no extra CLI tools (no flock(1), no lockfile, no filelock). Standard library is enough on macOS, Linux, and Windows alike.
  • The Agent tool must be available (for spawning research subagents). WebSearch / WebFetch are used by the subagents, not by this skill directly.

Inputs to Collect

  1. Which topic to drain. Read ## Research tracker → Topics: from CLAUDE.md.
    • One topic registered → use it.
    • Multiple topics → if the user named one, use that; otherwise ask which.
    • Zero topics → tell the user no topics are registered and stop.
  2. Batch size. Default 5. If the user asked for a different cap, honor it. Never exceed 5 in one run without explicit confirmation — parallel research burns tokens fast.

That's the entire input set.

The Atomic Write Protocol — read this once

Every modification of tasks.jsonl (claim, status flip, notes_path write) goes through the protocol documented at references/atomic_write_protocol.md. Read it before writing any code that touches tasks.jsonl. The summary:

  • Acquire an exclusive lock by os.open-ing tasks.jsonl.lock with O_CREAT | O_EXCL | O_WRONLY. The file's existence is the lock; its contents are unimportant. Acquire timeout: 5 seconds.
  • Modify the data: read the whole tasks.jsonl into memory, mutate, serialize to a temp file in the same directory, os.fsync, then os.replace the temp over the real file. (os.replace — not os.rename — because Windows.)
  • Release the lock by os.unlink-ing the lock file.
  • Wrap acquire/release in try/finally.

Read the full file on GitHub · 166 lines

Files

What ships with it

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

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. 5d ago First seen · 166 lines · 137 tokens per session scan A 30cea58c1c22

Subscribe to this mod's changes

local-research-runner is a skill published in the GitHub repository jbdamask/McBrain (2 stars, last pushed 2mo ago), licensed MIT. It adds 137 tokens to every session and 3,276 once invoked, about $0.0007 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