A publishing workflow for sending a finished chapter to Fanqie, a Chinese online-fiction publishing platform, after checking the chapter and login status.

Use it to prepare Fanqie access, publish the current manuscript chapter, handle first-time login or book identification, and verify the published result.

It checks that the correct final chapter exists and confirms the result with a screenshot, reducing uncertainty about whether publication worked.

publish — Skill for Claude Code and Codex by QQQingyu

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 QQQingyu/story-snack --skill publish

Clone the repo

git clone --depth 1 https://github.com/QQQingyu/story-snack

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/qqqingyu/story-snack/publish/github.svg)](https://agentmods.dev/skills/qqqingyu/story-snack/publish)

Your own site

<a href="https://agentmods.dev/skills/qqqingyu/story-snack/publish"><img src="https://agentmods.dev/badge/skills/qqqingyu/story-snack/publish/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/qqqingyu/story-snack/publish"><img src="https://agentmods.dev/badge/skills/qqqingyu/story-snack/publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 712 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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.00712
Opus 5	$0.00015	$0.00356
Sonnet 5	$0.00006	$0.00142
Haiku 4.5	$0.00003	$0.00071

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

Security

Grade A, and why

publish 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 11d 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.

skills/publish/SKILL.md · 68 lines

What it actually says

发布到番茄小说

将最新完成的章节发布到番茄小说作者平台。

前置检查

读取 clues/arc-progress.json 获取当前章节号 N
确认 manuscript/chapters/chapter-{NNN}.md 存在（章节已定稿）
如果文件不存在，提示用户先运行 /write-chapter

MCP 就绪检查

在发布前，确保 fanqie MCP 工具可用：

尝试调用 fanqie_check_login — 如果工具可用则跳过后续步骤
如果工具不可用，自动修复： a. 检查 mcp/fanqie/dist/index.js 是否存在
- 不存在 → 从 story-snack 源仓库复制 mcp/fanqie/，运行 cd mcp/fanqie && npm install && npm run build
- 已存在 → 跳到下一步 b. 检查是否存在项目级 MCP 配置文件（.claude/mcp.json）
- 不存在 → 创建 .claude/mcp.json：
```
{
  "mcpServers": {
    "fanqie": {
      "command": "node",
      "args": ["{当前项目绝对路径}/mcp/fanqie/dist/index.js"]
    }
  }
}
```
- 已存在但没有 fanqie 条目 → 追加 fanqie 配置 c. 告知用户：「MCP 配置已创建，请重启会话（Cmd+R 或重新进入项目目录）后再次运行 /publish」

发布流程

1. 检查登录

调用 fanqie_check_login
MCP 会自动启动 Chrome（使用独立 profile ~/.chrome-fanqie，不影响用户正常浏览器）
未登录 → 截图显示登录页，提示用户在自动打开的 Chrome 中手动登录（只需首次）
已登录 → 继续（固定 profile 保持登录态，后续无需再登录）

2. 读取章节并直接发布

读取 manuscript/chapters/chapter-{NNN}.md
提取章节标题和正文
不需要向用户确认标题或内容，直接发布
调用 fanqie_publish_chapter，传入 bookId、标题、正文

3. 截图确认

调用 fanqie_screenshot 截图确认
展示截图给用户
报告发布结果（成功/失败）

bookId 获取

首次发布时需要 bookId。优先从 memory 中读取，没有则问用户
bookId 在番茄作者后台的作品 URL 中：https://fanqienovel.com/main/writer/book/{bookId}

注意事项

发布流程全自动，不要中途暂停确认 — 读取章节后直接调用发布 API
如果发布失败，截图报错页面供排查

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.

11d ago First seen · 68 lines · 31 tokens per session scan A b02e2ca43911

Subscribe to this mod's changes

publish is a skill published in the GitHub repository QQQingyu/story-snack (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 712 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.

Writing and docs

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