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 Haohaha-11/Paper-Writing --skill research-scoutgit clone --depth 1 https://github.com/Haohaha-11/Paper-WritingWrote 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/haohaha-11/paper-writing/research-scout)<a href="https://agentmods.dev/skills/haohaha-11/paper-writing/research-scout"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/research-scout/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/haohaha-11/paper-writing/research-scout"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/research-scout.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00691 |
| Opus 5 | $0.00000 | $0.00345 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
research-scout 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 12d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Scout
Purpose
Build a field map from recent and classic papers before proposing or locking a paper idea.
When To Use
Use this skill at the beginning of a project, when the author has a broad topic, keyword set, dataset, domain problem, or preliminary observation but has not yet locked the research question.
Inputs
- Topic keywords and target domain.
- Target venue family if known.
- Seed papers, if available.
- User assets: datasets, compute, models, collaborators, evaluation access.
- Time window for recent papers and list of classic papers to inspect.
Procedure
- Build a question tree using
examples/research-query-tree-template.md. - Split the area into research threads, not model families only.
- Collect classic papers that define the problem, default assumptions, metrics, and evaluation workflow.
- Collect recent papers that represent the current frontier.
- For each paper, extract:
- problem addressed;
- default belief or assumption;
- diagnostic observation;
- method idea;
- evidence type;
- unresolved boundary.
- Build a frontier problem map.
- Mark crowded directions, under-tested assumptions, contradictory findings, missing diagnostics, and evaluation weaknesses.
- Tag every observation as source-backed, preliminary-result-backed, domain-expert-backed, hypothesis-only, or unchecked.
- Produce candidate problem seeds for
research-problem-framer.
Rubric
- The output distinguishes classic foundations from recent frontier work.
- The map is organized by problem and assumption, not by architecture names alone.
- Every candidate problem is traceable to at least one source or observation.
- The output identifies what is already solved, what is crowded, and what remains unresolved.
- The output avoids inventing citations, paper claims, or benchmark results.
Venue Adaptation
- ICLR/NeurIPS/ICML: emphasize assumptions, mechanisms, diagnostics, and generalization across tasks.
- CVPR/ECCV: emphasize visual evidence, dataset bias, benchmark saturation, and failure modes.
- AAAI: emphasize broad AI relevance, reasoning, interaction, society-facing constraints, or general task framing.
- IEEE TMI: emphasize clinical validity, multi-site robustness, privacy, and external validation.
- arXiv: preserve unresolved questions and source trail for later venue targeting.
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.
- 12d ago First seen · 87 lines · 0 tokens per session scan A 7a88fe5b2626
research-scout is a skill published in the GitHub repository Haohaha-11/Paper-Writing (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 691 tokens. 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
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…