agentmods.dev

professor-match

professor-match is a skill for Claude Code from xujingchen1996/research-app-toolkit. It costs 54 tokens per session (736 once invoked), scanned A, original, MIT.

A matching guide for finding potential PhD or research-degree supervisors whose work fits your interests and background.

In plain words
What is it for?
Use it to search for supervisors, compare their research areas, judge fit, and set application priorities. It can also add scientific background checks for life-science topics.
Why use it?
It helps narrow a large faculty list into realistic options while considering research fit and your application profile. Strong matches depend on having a CV or other background information.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the research-app-toolkit plugin — 9 skills, 9 commands, 1 agent, 1 hook shipped together

not rated 115repo +2 1mo ago A scan 54 tokens original MIT

Good fit Use it to search for supervisors, compare their research areas, judge fit, and set application priorities. It can also add scientific background checks for life-science topics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xujingchen1996/research-app-toolkit/professor-match
View source ↗ xujingchen1996/research-app-toolkit
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.

Any agent
npx skills add xujingchen1996/research-app-toolkit --skill professor-match
Clone the repo
git clone --depth 1 https://github.com/xujingchen1996/research-app-toolkit

Made for: Claude Code.

Or install research-app-toolkit, the plugin that ships this one along with the rest of its 9 skills, 9 commands, 1 agent, 1 hook.

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 professor-match

README.md
[![agentmods](https://agentmods.dev/badge/skills/xujingchen1996/research-app-toolkit/professor-match/github.svg)](https://agentmods.dev/skills/xujingchen1996/research-app-toolkit/professor-match)
Your own site
<a href="https://agentmods.dev/skills/xujingchen1996/research-app-toolkit/professor-match"><img src="https://agentmods.dev/badge/skills/xujingchen1996/research-app-toolkit/professor-match/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.

agentmods 80×15 button for professor-match

Your own site · 80×15
<a href="https://agentmods.dev/skills/xujingchen1996/research-app-toolkit/professor-match"><img src="https://agentmods.dev/badge/skills/xujingchen1996/research-app-toolkit/professor-match.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 736 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00054 $0.00736
Opus 5 $0.00027 $0.00368
Sonnet 5 $0.00011 $0.00147
Haiku 4.5 $0.00005 $0.00074

Measured 9d ago against content hash d940fe25f68e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

professor-match 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 9d 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.

codex/skills/professor-match/SKILL.md · 75 lines

How it starts

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

Professor Matching

Preconditions

  • Read ../../memory.md first.
  • If there is not yet a CV profile, prioritize suggesting that the user run cv-analyze first, because matching judgments depend on the user's background.

Language Rules

  • Support three output modes: zh, en, and bilingual.
  • If the user explicitly specifies a language, prioritize the current request.
  • Otherwise read preferred_language from memory.md.
  • If it is still unclear, follow the user's current conversation language.
  • Original English proper nouns from professor homepages, school programs, and similar search materials may be retained, but explanatory text should follow the selected output language.

Optional Linkage: Life Science Research

  • If the user's application direction clearly falls under life sciences / biomedical research, such as genetics, functional genomics, immunology, neuroscience, cancer biology, cell biology, or translational medicine, and the current task needs research-direction grounding, then link life-science-research.
  • This is suitable for linkage in scenarios such as:
    • needing to first clarify target / gene / disease / pathway background
    • needing to judge professor fit based on public literature, datasets, or recent research trajectories
    • needing to start from the research-problem space rather than only searching professors by keywords
  • The linkage result should be used primarily to:
    • narrow research keywords
    • judge the natural bridge between the professor's recent work and the user's background
    • identify more specific research-fit narratives
  • If the user only wants routine professor search by school / country / project name, or only wants ranking updates, do not trigger that linkage.

Fill In the Search Conditions First

If the user's request is not specific enough, fill in at least the following information:

  • research direction or keywords
  • target country / region / school scope
  • degree type and enrollment time
  • special constraints, such as "must be recently recruiting students", "prefer industry collaboration", or "want full funding"

Read the full file on GitHub · 75 lines

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. 9d ago First seen · 75 lines · 54 tokens per session scan A d940fe25f68e

Subscribe to this mod's changes

professor-match is a skill published in the GitHub repository xujingchen1996/research-app-toolkit (115 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 736 once invoked, about $0.0003 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.

Research
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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens