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 tranfu-labs/tranfu-skills --skill research-keywordsgit clone --depth 1 https://github.com/tranfu-labs/tranfu-skillsWrote 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/tranfu-labs/tranfu-skills/research-keywords)<a href="https://agentmods.dev/skills/tranfu-labs/tranfu-skills/research-keywords"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/research-keywords/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/tranfu-labs/tranfu-skills/research-keywords"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/research-keywords.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.00152 | $0.02681 |
| Opus 5 | $0.00076 | $0.01340 |
| Sonnet 5 | $0.00030 | $0.00536 |
| Haiku 4.5 | $0.00015 | $0.00268 |
Grade A, and why
research-keywords 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
关键词调研
把英文种子词或已有关键词主题转成可复核的搜索、竞品和收入证据，并给出是否进入候选项目的处理结论。默认先研究全球英文市场，不限定行业或产品形态。
When to use
处理关键词证据验证、竞品与收入调查、Lark 调研表填写和候选项目交接。它可以接收 discover-keyword-seeds 的交接包，也可以从用户给出的现成关键词、竞品网址或 Search Console 查询开始。
同类 Skill 对比
由 tranfu-publish 起草，作者签字。帮助阅读者横向决定要装哪个或跳到更合适的同类。
公司库内
- discover-keyword-seeds — 从机会锚点生成结构化种子词；本 skill 区别：继续收集真实证据并填写调研表。
- market-analysis — 做行业规模、竞争格局和市场机会分析；本 skill 区别：按关键词主题和固定字段形成可立项输入。
- seo-audit — 审计单页面技术和内容 SEO；本 skill 区别：研究做什么产品，不审计已有页面质量。
外部世界
- semrush-seo — 通过 Semrush API 查询关键词和竞品数据；本 skill 区别：同时纳入 Search Console、收入证据和候选项目规则。
- Agentic SEO Skill — 做网站与页面 SEO 审计；本 skill 区别：在开发前判断关键词商业机会。
- ecommerce-keyword-research — 研究电商平台关键词；本 skill 区别：覆盖工具、API、企业服务、报告、撮合和人工服务。
本 skill 独特价值
- 搜索和收入证据同时判断
- 按用户问题聚类而非单词
- 直接衔接 Lark 候选项目
使用技巧
由 tranfu-publish 引导起草。帮助阅读者纵向上手；横向比较见上方同类 Skill 对比。
材料方案
- 最好提供种子词交接包
- 现成关键词或竞品也能开始
- 默认使用全球英文和 US 库
推荐用法
- 复用已登录的研究工具
- 每个数字都保留日期和来源
- 先主题聚类，再批量查数据
已知限制
- 公开资料不等于真实利润
- 无权限时不能读取私有数据
- 只创建待评审，不批准立项
前置输入
优先读取以下材料；缺少部分材料时，从已有输入继续，并明确未验证项。
- 种子词交接包、现成关键词主题、竞品网址或 Search Console 查询。
- 机会锚点及用户—任务—结果说明。
- 目标市场；默认全球英文，Semrush 首轮默认 US 数据库。
- 调研表和候选项目表入口；需要写入时确认当前身份有权限。
- 用户指定的排除范围或时间要求。
工具选择
按当前环境选择可用入口，不把某一种接入方式当作前置条件：
- Semrush：优先使用可调用的 Semrush 工具；没有接口时使用已登录网页。
- Search Console：使用已登录页面读取真实查询、页面、点击、曝光和排名。
- Google 与 Google Trends：核对搜索结果、广告、产品页、收费页和趋势性质。
- 公开资料：查询项目收费、客户案例、协议收入、公司披露和可信第三方数据。
- Lark：优先使用 Base 能力按字段写入；不具备时输出可直接人工录入的结构化记录。
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 181 lines · 152 tokens per session scan A 052b0ab019b5
research-keywords is a skill published in the GitHub repository tranfu-labs/tranfu-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 152 tokens to every session and 2,681 once invoked, about $0.0008 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-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…