Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moberghr/mtk-agent-toolkit/main/.claude/skills/research-context/SKILL.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/research-context)<a href="https://agentmods.dev/skills/moberghr/mtk-agent-toolkit/research-context"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/research-context/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/moberghr/mtk-agent-toolkit/research-context"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/research-context.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 Agent Snooping · line 137 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00990 |
| Opus 5.5 | $0.00016 | $0.00396 |
| Sonnet 5.5 | $0.00008 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
research-context 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 16d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Context
Overview
Answers "given what this repo already does, what is the current way to do X?" with fresh external information, grounded against named files in this repo. The output is a short cited brief consumed by spec-driven-development (the version-sensitive ambiguity gate) and implement (Phase 3).
Tool discipline (phase-locked):
Read/Grep/GlobandWebSearch/WebFetchonly. Never edit source or test code; the only artifact is the brief. Runs onsonnetper.claude/references/model-routing.md.
When To Use
- A spec or plan hinges on a version-sensitive choice, a recent library landscape, a migration path, or current security advisories; or the engineer asks to "research X".
- Not for a known-API question answerable from local sources (read the SDK source or in-repo docs), and not for this codebase's internals (read the code).
Workflow
- Ground before any web call. Resolve the stack (
bash scripts/resolve-tech-stack.sh "<path>"), read the installed version from the lockfile or project file, and name 1–3 files showing current usage. Frame it: "For <stack> using <library>@<installed-version>, given this repo does <X in file:line>, what is the current recommended way to <goal>?" If the version or a grounding file cannot be found, the brief says so. - Pick depth. Light path by default:
WebSearch+WebFetch(2–4 fetches) orcontext7. Deep path only for contested or high-stakes questions (security, data integrity, hard-to-reverse migrations): 2–4 parallel research subagents, one angle each. A claim only one subagent found, or that they disagree on, stays[ASSUMED]until a fetched source settles it. Without subagents, run the angles sequentially and say so. - Tag every claim with exactly one tag:
[CITED:<url>]— a fetched source. Memory is not a source.[VERIFIED:<file:line>]— confirmed against this repo and the installed version.[ASSUMED]— not confirmed, including any finding for a different major/minor version than the one installed.
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.
- 16d ago Changed · -99 lines ce83f36d03ba
- 1mo ago Changed · -10 lines 41e078c6c538
- 2mo ago First seen · 167 lines · 40 tokens per session scan A bb271895671a
research-context is a skill published in the GitHub repository moberghr/mtk-agent-toolkit (9 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 990 once invoked, about $0.0002 per session on Opus 5.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.
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…