cheat-publish

cheat-publish is a skill for Claude Code, Codex from XBuilderLAB/cheat-on-content. It costs 0 tokens per session (2,199 once invoked), scanned A, original, MIT.

A small publishing-record procedure for prediction files, where it saves a published URL, platform, and time in metadata. It also updates the project's state file without changing the prediction text.

In plain words
What is it for?
Registering published YouTube, Bilibili, Douyin, or Xiaohongshu content, updating its metadata, and clearing the related in-progress session.
Why use it?
It keeps track of where and when a prediction was published while protecting the original prediction from accidental edits. It can identify the platform from supported URL patterns.

Skill for Claude CodeCodex

About the project

Cheat on Content is a workflow for content creators that records predictions and results for each post, reviews performance later, and updates the criteria used for future decisions. It is intended to make content planning and publishing an experiment that becomes more informed over time. The catalogue contains the skills that implement this workflow.

XBuilderLAB/cheat-on-content · 6,756 stars · on GitHub

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.

agentmods
npx agentmods add skills/xbuilderlab/cheat-on-content/cheat-publish
Any agent
npx skills add XBuilderLAB/cheat-on-content --skill cheat-publish
Clone the repo
git clone --depth 1 https://github.com/XBuilderLAB/cheat-on-content

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.

agentmods badge for cheat-publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/xbuilderlab/cheat-on-content/cheat-publish.svg)](https://agentmods.dev/skills/xbuilderlab/cheat-on-content/cheat-publish)
Your own site
<a href="https://agentmods.dev/skills/xbuilderlab/cheat-on-content/cheat-publish"><img src="https://agentmods.dev/badge/skills/xbuilderlab/cheat-on-content/cheat-publish.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,199 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.02199
Opus 5 $0.00000 $0.01099
Sonnet 5 $0.00000 $0.00440
Haiku 4.5 $0.00000 $0.00220

Measured 5d ago against content hash ba810234e03f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cheat-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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/cheat-publish/SKILL.md · 171 lines

How it starts

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

/cheat-publish — 发布登记

把作品的发布元数据(URL、发布时间、平台)补到预测文件 header 与 state file。禁止改预测段——hook 会拦。

Overview

[用户:已发布 https://...]
  ↓
[Phase 0: 找到对应的预测文件]   ← 通过 in_progress_session 或匹配
  ↓
[Phase 1: 解析 URL → 平台/发布时间]
  ↓
[Phase 2: 更新 prediction 文件 header(仅 metadata 段)]
  ↓
[Phase 3: 更新 .cheat-state.json,清除 in_progress_session]

Constants

  • AUTO_DETECT_PLATFORM = true — 从 URL 模式自动识别平台
  • VERIFY_BLIND = true — 提醒用户:从此刻起看到任何后续数据都会破坏盲度声明的诚信

Inputs

必填 来源
<prediction-file> 或 URL 用户参数;缺失则用 .cheat-state.jsonin_progress_session.file
.cheat-state.json 用户项目根

Workflow

Phase 0: 找到对应的预测文件

按优先级:

  1. 用户参数明确给了 prediction 文件路径 → 用它
  2. 用户参数只给了 URL → 读 .cheat-state.jsonin_progress_session.file
  3. 都没有 → 列出 predictions/*.md 中 header 没填 published_at 的文件,让用户选

警告路径:若 in_progress_session.file 与用户给的 URL 时间差超过 14 天 → 提示"这个预测写于很久之前,确认是这篇?"

Phase 1: 解析平台

AUTO_DETECT_PLATFORM=true 时按 URL 模式:

URL 模式 平台
youtube.com/* youtu.be/* youtube
bilibili.com/* b23.tv/* bilibili
douyin.com/* iesdouyin.com/* v.douyin.com/* douyin
xiaohongshu.com/* xhslink.com/* xhs
mp.weixin.qq.com/* wechat
substack.com/* *.substack.com/* substack
medium.com/* *.medium.com/* medium
twitter.com/* x.com/* twitter
其他 unknown — 询问用户

发布时间获取:

  • 不强求自动抓——绝大多数平台需要登录态
  • 询问用户:"发布时间是?(默认:现在)" → 接受 ISO 8601 或自然语言("今天 14:30" / "20 分钟前")
  • 解析失败 → 用 now()

Phase 2: 更新 prediction 文件 header

绝不触碰 ## 预测 段及之后。只动文件最顶部的 metadata 块。

读文件,定位到 metadata 块(在第一个 ## 之前的所有行)。检查是否已有这些字段——有则警告"已登记过"并询问是否覆盖;无则追加:

**Published at**: 2026-05-04T14:32:00+08:00
**Platform**: douyin
**URL**: https://v.douyin.com/abc123
**Video Folder**: videos/2026-05-04_a3f2c1d4_停止期待/
**Aweme ID**: 7234567890123456789  (douyin / 视频号 等需要的 platform-specific ID)

关于 platform-specific ID

  • 抖音:从 URL 短链 resolve 后提取 aweme_id(v.douyin.com → 重定向后含 modal_id 或 item_id 参数)
  • B 站:BV 号
  • 小红书:note_id
  • YouTube:v= 参数后的 video_id

Read the full file on GitHub · 171 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. 5d ago First seen · 171 lines · 0 tokens per session scan A ba810234e03f

Subscribe to this mod's changes

cheat-publish is a skill published in the GitHub repository XBuilderLAB/cheat-on-content (6,756 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,199 tokens. 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.

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

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 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