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 WALKERKILLER/Look-Tongji-Notes --skill pagegit clone --depth 1 https://github.com/WALKERKILLER/Look-Tongji-NotesWrote 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/walkerkiller/look-tongji-notes/page)<a href="https://agentmods.dev/skills/walkerkiller/look-tongji-notes/page"><img src="https://agentmods.dev/badge/skills/walkerkiller/look-tongji-notes/page/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/walkerkiller/look-tongji-notes/page"><img src="https://agentmods.dev/badge/skills/walkerkiller/look-tongji-notes/page.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.00028 | $0.00603 |
| Opus 5 | $0.00014 | $0.00302 |
| Sonnet 5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
page 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 10d 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
Page (GitHub Pages 部署)
将已构建的课程 wiki 静态站点部署到 GitHub Pages。
When to Use
- User says
/pageor "deploy to pages" or "publish wiki". - After running
/wiki buildand thesite/directory is ready.
Workflow
1. 前置检查 A: gh CLI 已安装
gh --version
如未安装，输出安装指引，引导用户访问 https://cli.github.com/ 安装。
2. 前置检查 B: gh 已认证
gh auth status
如未认证，引导用户执行 gh auth login 完成 GitHub 认证。
3. 前置检查 C: site/ 已构建
检查 workspace 的 site/index.html 是否存在：
ls <WORKSPACE_ROOT>/site/index.html
如 site/ 不存在或为空，引导先运行 /wiki build 构建站点。
4. 确定部署目标 repo
优先使用环境变量 GH_PAGES_REPO：
echo $GH_PAGES_REPO
如果未设置，从当前 git remote 推断：
git remote get-url origin
用户可在 .env 中设置 GH_PAGES_REPO=owner/repo 来指定目标仓库。
5. 部署到 gh-pages 分支
gh pages deploy <WORKSPACE_ROOT>/site/ --repo <TARGET_REPO> --branch gh-pages
要求 gh CLI 版本 >= 2.29.0。
6. 输出结果
部署完成后，GitHub Pages URL 格式为 https://<owner>.github.io/<repo>/。
Requirements
- gh CLI >= 2.29.0（安装: https://cli.github.com/）
- 已完成
gh auth login - workspace 的
site/已通过/wiki build构建 - 目标 GitHub repo 已启用 GitHub Pages
Where <SKILL_DIR> Points
<SKILL_DIR> is the directory containing this SKILL.md. The /page command uses the gh CLI directly (no shared Python scripts needed). For other skills, shared scripts (look_tongji.py, timeline_tools.py, tongji_backend/) and references live two levels up in the repository root (<SKILL_DIR>/../../scripts/ and <SKILL_DIR>/../../references/).
What ships with it
1 file 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.
- 10d ago First seen · 85 lines · 28 tokens per session scan A c65dcc4ac4f4
page is a skill published in the GitHub repository WALKERKILLER/Look-Tongji-Notes (41 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 603 once invoked, about $0.0001 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…
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…