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 agentmods add skills/childrentime/reactuse/publish-hashnodenpx skills add childrentime/reactuse --skill publish-hashnodegit clone --depth 1 https://github.com/childrentime/reactuseWhat 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 | $0.00134 | $0.03919 |
| Opus 5 | $0.00067 | $0.01959 |
| Sonnet 5 | $0.00027 | $0.00784 |
| Haiku 4.5 | $0.00013 | $0.00392 |
Grade A, and why
publish-hashnode scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl` 直接打 reactuse.hashnode.dev 会被 Cloudflare bot challenge 拦（HTTP 403），必须走浏览器 session。 How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
publish-hashnode — 跨发到 Hashnode
reactuse.com 的博客在 Hashnode 有镜像 reactuse.hashnode.dev。每篇新文章都应该同步过去：
- canonical URL 指回 reactuse.com（不抢 SEO 权重）
- Hashnode 流量是真实增量（独立 RSS/订阅用户）
⚠️ 唯一路径：浏览器自动化
Hashnode 在 2026-05-13 把 GraphQL API 转成了付费 + allow-list 制（参见 https://hashnode.com/announcements/graphql-api），`reactuse.hashnode.dev` 没在白名单里。老的 scripts/publishHashnode.mjs 已经在 2026-05-18 删掉，不要重写一个；除非将来真的付费拿到 allow-list（届时再考虑），否则就老老实实走 opencli 浏览器路径。
触发场景
- 用户明说："发到 hashnode" / "publish to hashnode" / "把这篇 cross-post 一下"
- 用户刚写完一篇博客，并说"发出去" / "同步发布" / "推平台"——默认包括 Hashnode
- 多平台分发流程的一步（dev.to + Medium + Hashnode + 掘金）
- 补发历史文章："把上一篇也发到 hashnode" / "把 post-N 那篇推到 hashnode"
⚠️ 不要触发：
- 用户只让发 Medium / dev.to / 掘金 —— 不要顺手也发 Hashnode
- 用户说"草稿" / "draft" —— 网页流程默认是直接 Publish，要 draft 留草稿就不要点最后那下 Publish
前置检查
opencli --version # 需要 ≥ 1.7.22（1.7.18 之前 `--session` 是 flag，1.7.22 改成了位置参数）
opencli doctor # 必须看到 Connectivity: connected
如果版本旧：npm install -g @jackwener/opencli 然后 opencli daemon restart。注意 CLI 形态变化：1.7.22+ 用 opencli browser <session> <command>（位置参数），旧版是 opencli browser --session <session> <command>。本 SKILL.md 的命令是新形态。
如果 Connectivity: failed (operation aborted)：让用户把 Chrome 切到前台、点一下 opencli 扩展图标唤醒 service worker，再 opencli doctor。
工作流程
步骤 1：确认目标文章 + 提取元数据
ls packages/website-astro/src/content/blog/ | tail -3 # 看最新一批
从 packages/website-astro/src/content/blog/{date}-{slug}.md 的 frontmatter 拿到：
title— 文章标题slug— 用作 Hashnode 的 URL 段，也用来拼 canonicaltags— 前 3 个用作 Hashnode tag（Hashnode tag 必须是已存在的，要从下拉里挑）
canonical URL = https://reactuse.com/blog/{slug}/（结尾斜杠必加）
步骤 2：到草稿编辑器
坑点：不要 open https://hashnode.com/new —— 会被 Hashnode 解析成用户名 @new（确实有这个用户）。
正确路径：
opencli browser default open "https://hashnode.com/drafts"
opencli browser default state # 看页面
# 找到 [N]<button><span>New</span></button>，N 是 ref 编号
opencli browser default click <N> # 进新草稿
opencli browser default get url # 应是 /draft/<id>
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.
- 2d ago First seen · 262 lines · 134 tokens per session scan A d439ea3cde6b
publish-hashnode is a skill published in the GitHub repository childrentime/reactuse (1,048 stars, last pushed 12d ago), licensed Unlicense. It adds 134 tokens to every session and 3,919 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
react-hooks-composition
Advanced React hooks composition patterns - SWR integration, debounced search, memoized contexts, state machines, and performance optimization.
juniors-best-practice
Juniors-focused React and TypeScript best practices. Use this skill when writing or reviewing code to enforce clear, consistent, and maintainable patterns across common scopes like React, TypeScript, styling, devtools, assets, and Git.
react-hooks-best-practices
React hooks best practices for React application code and custom hook design across DX, optimization, and logic. Use when writing components with hooks, creating or refactoring custom hooks, reviewing hook usage/APIs/internals, checking effects/dependencies/state/refs/callbacks, or improving hook correctness…
reactuse
Practical playbook for React teams to choose and apply reactuse hooks across state, async flows, browser APIs, and UI interactions. Use it when replacing custom hook logic with production-ready patterns that stay compatible with SSR and Next.js.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".