wechatbot: Skill for Claude Code

.pi/skills/publish/SKILL.md

publish is a skill for Claude Code, Codex from corespeed-io/wechatbot. It costs 37 tokens per session (2,039 once invoked), scanned A, original, MIT.

Release instructions for publishing Node.js packages to npm and a Python package to PyPI, which are package registries developers use to share software.

In plain words
What is it for?
Use them to release the listed JavaScript and Python packages through their GitHub Actions workflows and version-tag process.
Why use it?
They help prevent incomplete releases by checking versions, tests, builds, commits, and tags before publishing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is corespeed-io/wechatbot's own configuration. It tells Claude Code and Codex how to work on wechatbot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything wechatbot configures →

Reuse

Borrowing it

Nothing to install: this file belongs to corespeed-io/wechatbot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/corespeed-io/wechatbot/main/.pi/skills/publish/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/corespeed-io/wechatbot

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 publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/corespeed-io/wechatbot/publish/github.svg)](https://agentmods.dev/skills/corespeed-io/wechatbot/publish)
Your own site
<a href="https://agentmods.dev/skills/corespeed-io/wechatbot/publish"><img src="https://agentmods.dev/badge/skills/corespeed-io/wechatbot/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.

agentmods 80×15 button for publish

Your own site · 80×15
<a href="https://agentmods.dev/skills/corespeed-io/wechatbot/publish"><img src="https://agentmods.dev/badge/skills/corespeed-io/wechatbot/publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,039 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00037 $0.02039
Opus 5.5 $0.00015 $0.00816
Sonnet 5.5 $0.00007 $0.00408
Haiku 4.5 $0.00004 $0.00204

Measured 2mo ago against content hash 166df7c1fc74, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.pi/skills/publish/SKILL.md · 206 lines

How it starts

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

Publish Packages

This project has two publishable packages with separate GitHub Actions workflows:

Package Registry Directory Workflow Tag pattern
@wechatbot/wechatbot npm nodejs/ .github/workflows/publish-npm.yml node-v*
@wechatbot/pi-agent npm pi-agent/ .github/workflows/publish-pi-agent.yml pi-agent-v*
wechatbot-sdk PyPI python/ .github/workflows/publish-pypi.yml py-v*

Pre-publish Checklist

Before publishing, verify the following:

  1. Version is bumped — ensure the version in the package manifest is updated:
    • npm: nodejs/package.json → "version" field
    • PyPI: python/pyproject.toml → [project] version field
  2. Tests pass — run tests locally before tagging:
    • npm: cd nodejs && npm test
    • PyPI: cd python && pytest
  3. Build succeeds — verify the package builds cleanly:
    • npm: cd nodejs && npm run build
    • PyPI: cd python && python -m build
  4. Changes are committed and pushed to the main branch

Publishing via Git Tag

Create and push a tag to trigger the GitHub Actions workflow:

Publish Node.js to npm

# 1. Bump version in nodejs/package.json
# 2. Commit the change
git add nodejs/package.json
git commit -m "chore: bump node package to vX.Y.Z"
git push

# 3. Tag and push
git tag node-vX.Y.Z
git push origin node-vX.Y.Z

Publish Python to PyPI

# 1. Bump version in python/pyproject.toml
# 2. Commit the change
git add python/pyproject.toml
git commit -m "chore: bump python package to vX.Y.Z"
git push

# 3. Tag and push
git tag py-vX.Y.Z
git push origin py-vX.Y.Z

Publishing via Manual Dispatch

Both workflows support manual triggering from GitHub Actions UI with a dry run option:

  1. Go to the repo → Actions tab
  2. Select Publish to npm or Publish to PyPI
  3. Click Run workflow
  4. Optionally enable Dry run to test without actually publishing
    • npm dry run: runs npm publish --dry-run
    • PyPI dry run: publishes to TestPyPI instead of PyPI

Read the full file on GitHub · 206 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. 2mo ago First seen · 206 lines · 37 tokens per session scan A 166df7c1fc74

Subscribe to this mod's changes

publish is a skill published in the GitHub repository corespeed-io/wechatbot (695 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 2,039 once invoked, about $0.0001 per session on Opus 5.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.

Related

publish compared with skills from other repositories

publish next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
publishcorespeed-io/wechatbotSkill6954d agoMITA37Claude Code, Codex
release-announcementpaperclipai/paperclipSkill111kyesterdayMITA42Claude Code, Codex
releasethedotmack/claude-memSkill114kyesterdayApache-2.0A13Claude Code
release-notesphuryn/pm-skillsSkill28k8d agoMITA57Claude Code
multi-agent-release-managerchromium/chromiumSkill25kyesterdayBSD-3-ClauseA27Claude Code, Codex
pack-submitaeonfun/aeonSkill788yesterdayMITA27Claude Code, Codex
updater_guidesiddsachar/row-botSkill1.7kyesterdayApache-2.0A22Claude Code, Codex