Borrowing it
Nothing to install: this file belongs to deandevz/king-context. 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/deandevz/king-context/main/.agents/skills/king-research/SKILL.mdgit clone --depth 1 https://github.com/deandevz/king-contextWrote 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/deandevz/king-context/king-research)<a href="https://agentmods.dev/skills/deandevz/king-context/king-research"><img src="https://agentmods.dev/badge/skills/deandevz/king-context/king-research.svg" alt="Measured on agentmods" height="20"></a>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.00124 | $0.01697 |
| Opus 5 | $0.00062 | $0.00848 |
| Sonnet 5 | $0.00025 | $0.00339 |
| Haiku 4.5 | $0.00012 | $0.00170 |
Grade A, and why
king-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 7d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
King Research — Topic Research Skill
Invoke king-research to build a research corpus on any topic. The user describes what they want; you extract the topic, pick the effort mode, and run the pipeline.
When to use this skill
| User wants... | Use |
|---|---|
| Sources on an open-web topic (papers, blog posts, discussions) | king-research (this skill) |
| A specific product/API doc site scraped | scraper-workflow (king-scrape) |
| To query already-indexed content | king-context (kctx search) |
If the user already mentions a URL or a specific product's docs, hand off to scraper-workflow.
Step 1: Extract the topic
Pull the topic from the user's message as a concise phrase (2–6 words).
Rules:
- Strip filler: "please", "por favor", "pode fazer", "quero que", "me faça".
- Keep semantic qualifiers: "for RAG pipelines", "in production", "2025".
- Prefer the user's wording over paraphrase.
- Quote multi-word topics when passing to the CLI.
If the topic is vague (e.g. "faz um research aí", "pesquise algo"), ask ONE clarifying question before running: "What topic?"
Step 2: Pick the effort mode
Explicit signals (override inference)
| Signal in the user's message | Mode |
|---|---|
| "rápido", "quick", "basic", "só uma ideia", "overview", "simples" | --basic |
| (no qualifier) | --medium (default) |
| "detalhado", "aprofundado", "profundo", "detailed", "in-depth", "completo" | --high |
| "exaustivo", "estado da arte", "thorough", "comprehensive", "state of the art", "máximo", "tudo que tiver" | --extrahigh |
Inferred from complexity (when no explicit signal)
| Topic shape | Mode |
|---|---|
| Narrow, well-known (e.g. "httpx timeouts") | --basic |
| Standard technical topic (e.g. "prompt caching strategies") | --medium (default) |
| Broad or comparative (e.g. "RAG vs fine-tuning") | --high |
| Bleeding-edge / multi-domain survey (e.g. "mixture of experts state of the art 2025") | --extrahigh |
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.
- 7d ago First seen · 168 lines · 124 tokens per session scan A cc6d11efcbf2
king-research is a skill published in the GitHub repository deandevz/king-context (52 stars, last pushed 3mo ago), licensed MIT. It adds 124 tokens to every session and 1,697 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…