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 LigphiDonk/Oh-my--paper --skill research-pipeline-plannergit clone --depth 1 https://github.com/LigphiDonk/Oh-my--paperWrote 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/ligphidonk/oh-my--paper/research-pipeline-planner)<a href="https://agentmods.dev/skills/ligphidonk/oh-my--paper/research-pipeline-planner"><img src="https://agentmods.dev/badge/skills/ligphidonk/oh-my--paper/research-pipeline-planner/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/ligphidonk/oh-my--paper/research-pipeline-planner"><img src="https://agentmods.dev/badge/skills/ligphidonk/oh-my--paper/research-pipeline-planner.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.00003 | $0.00397 |
| Opus 5 | $0.00002 | $0.00198 |
| Sonnet 5 | $0.00001 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
Research Pipeline Planner 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 13d 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.
What it actually says
Research Pipeline Planner
Use this skill when the user needs to define or revise the project-level research pipeline.
Goals
- clarify the research topic, target venue, and expected contribution
- set or revise the starting stage
- update
.pipeline/docs/research_brief.json - update
.pipeline/tasks/tasks.json
Working Rules
- Read
instance.json,.pipeline/docs/research_brief.json, and.pipeline/tasks/tasks.jsonfirst if they exist. - Keep the pipeline aligned with the five stages: survey, ideation, experiment, publication, promotion.
- When the user already has results or a draft, move the starting stage forward instead of rebuilding earlier stages.
- Do not invent citations, datasets, or experimental outcomes.
- When entering ideation stage, use the
research-idea-convergenceskill to generate candidate directions and let the user choose. Never autonomously decide the research direction. - Ensure every stage transition involves a user checkpoint — do not skip stages or auto-advance without user confirmation.
- 严格线性执行：任务必须按顺序执行，当前任务未完成前不得跳至下一任务。调研未完成 → 不得进入构思；构思未完成 → 不得进入实验。每个阶段的所有任务 done 后才能进入下一阶段。
Expected Outputs
- a concise research brief with topic, goal, venue, current stage, and stage notes
- a task list with dependencies, suggested skills, and a concrete
nextActionPrompt - for ideation: candidate directions presented via
research-idea-convergencebefore anypublishable_angle.mdis written
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.
- 13d ago First seen · 35 lines · 3 tokens per session scan A 552aa187ae94
Research Pipeline Planner is a skill published in the GitHub repository LigphiDonk/Oh-my--paper (727 stars, last pushed 5mo ago), licensed MIT. It adds 3 tokens to every session and 397 once invoked, about $0.0000 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…