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 alizeeblack-code/zhihu-mcp --skill track-zhihu-usergit clone --depth 1 https://github.com/alizeeblack-code/zhihu-mcpWrote 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/alizeeblack-code/zhihu-mcp/track-zhihu-user)<a href="https://agentmods.dev/skills/alizeeblack-code/zhihu-mcp/track-zhihu-user"><img src="https://agentmods.dev/badge/skills/alizeeblack-code/zhihu-mcp/track-zhihu-user/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/alizeeblack-code/zhihu-mcp/track-zhihu-user"><img src="https://agentmods.dev/badge/skills/alizeeblack-code/zhihu-mcp/track-zhihu-user.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.00043 | $0.01028 |
| Opus 5 | $0.00022 | $0.00514 |
| Sonnet 5 | $0.00009 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
track-zhihu-user 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.
What it actually says
知乎用户追踪
获取知乎用户的资料和最新动态,分析其活跃度和内容偏好。
适用场景
- 用户说"帮我看看 XXX 最近在知乎上做了什么"
- 关注某个 KOL 或行业专家的知乎动态
- 竞品创始人/核心成员的舆情监控
- 定期追踪某用户的内容更新
工作流程
用户输入用户 URL token 或主页链接
│
├─ Step 1: 解析输入,获取 user token
│
├─ Step 2: 获取用户资料
│
├─ Step 3: 抓取最新动态
│
├─ Step 4: 深入阅读重点内容(可选)
│
└─ Step 5: 输出用户画像/动态报告
Step 1: 解析输入
从用户输入中提取 URL token:
- 主页链接
https://www.zhihu.com/people/xu-ze-qiu→ token =xu-ze-qiu - 直接给 token
xu-ze-qiu→ 直接使用 - 用户名不是 token,需要提醒用户去主页获取 URL 中的 token
Step 2: 获取用户资料
user_profile(token="xu-ze-qiu")
获取:
- 用户名、一句话介绍、个人简介
- 关注数、粉丝数、获赞数
- 回答数、文章数、提问数
- 最近活跃的内容
Step 3: 抓取最新动态
get_activities(user="xu-ze-qiu", count=10)
获取用户最近的活动(回答问题、发表文章、赞同内容等),包含:
- 活动标题和链接
- 活动摘要
- 时间
活动会自动存入本地数据库,方便后续查询历史。
查看历史动态
如果需要查看之前抓取过的数据:
get_new_since(hours=168, user="xu-ze-qiu")
这会查询数据库中最近 N 小时内该用户的活动记录(无需再次爬取)。
Step 4: 深入阅读重点内容(可选)
如果用户关心某条动态的具体内容,根据链接类型调用对应工具:
- 回答链接 →
get_answer_detail(question_id, answer_id) - 文章链接 →
get_article_detail(article_id) - 问题链接 →
get_question_detail(question_id)
从链接中解析 ID:
zhihu.com/question/123/answer/456→ question_id=123, answer_id=456zhuanlan.zhihu.com/p/789→ article_id=789zhihu.com/question/123→ question_id=123
Step 5: 输出报告
首次追踪(用户画像)
## 知乎用户:{用户名}
> {一句话介绍}
### 基本信息
- 关注:{关注数} · 粉丝:{粉丝数}
- 获赞:{获赞数}
- 回答:{回答数} · 文章:{文章数}
### 个人简介
{个人简介}
### 最近动态({N} 条)
1. [{标题}]({链接}) — {时间}
{摘要}
2. ...
### 活跃领域分析
根据最近动态的话题分布:
- 领域 1:XX 条相关内容
- 领域 2:XX 条相关内容
持续监控(动态更新)
## {用户名} 的最新动态
> 上次检查:{时间} · 新增 {N} 条活动
### 新动态
1. [{标题}]({链接}) — {时间}
{摘要}
### 数据库统计
- 累计追踪:{总活动数} 条
- 追踪时长:{天数} 天
注意事项
get_activities是实时爬取,每次调用会启动浏览器访问知乎,注意频率get_new_since只查本地数据库,速度快且不触发反爬- 用户 token 区分大小写,必须从 URL 中获取(不是显示的用户名)
- 如果用户设置了隐私保护,部分信息可能无法获取
- 持续监控建议间隔 1 小时以上,避免频繁爬取触发风控
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.
- 9d ago First seen · 142 lines · 43 tokens per session scan A 56b7074b0193
track-zhihu-user is a skill published in the GitHub repository alizeeblack-code/zhihu-mcp (4 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 1,028 once invoked, about $0.0002 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…
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…
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…
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…