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.
curl -O https://raw.githubusercontent.com/corespeed-io/wechatbot/main/.pi/skills/publish/SKILL.mdgit clone --depth 1 https://github.com/corespeed-io/wechatbotWrote 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/corespeed-io/wechatbot/publish)<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.
<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>- NVIDIA SkillSpector pass
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.00037 | $0.02039 |
| Opus 5.5 | $0.00015 | $0.00816 |
| Sonnet 5.5 | $0.00007 | $0.00408 |
| Haiku 4.5 | $0.00004 | $0.00204 |
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.
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:
- Version is bumped — ensure the version in the package manifest is updated:
- npm:
nodejs/package.json→"version"field - PyPI:
python/pyproject.toml→[project] versionfield
- npm:
- Tests pass — run tests locally before tagging:
- npm:
cd nodejs && npm test - PyPI:
cd python && pytest
- npm:
- Build succeeds — verify the package builds cleanly:
- npm:
cd nodejs && npm run build - PyPI:
cd python && python -m build
- npm:
- 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:
- Go to the repo → Actions tab
- Select Publish to npm or Publish to PyPI
- Click Run workflow
- 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
- npm dry run: runs
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.
- 2mo ago First seen · 206 lines · 37 tokens per session scan A 166df7c1fc74
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.
publish compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| publishcorespeed-io/wechatbot | Skill | 695 | 4d ago | MIT | A | 37 | Claude Code, Codex |
| release-announcementpaperclipai/paperclip | Skill | 111k | yesterday | MIT | A | 42 | Claude Code, Codex |
| releasethedotmack/claude-mem | Skill | 114k | yesterday | Apache-2.0 | A | 13 | Claude Code |
| release-notesphuryn/pm-skills | Skill | 28k | 8d ago | MIT | A | 57 | Claude Code |
| multi-agent-release-managerchromium/chromium | Skill | 25k | yesterday | BSD-3-Clause | A | 27 | Claude Code, Codex |
| pack-submitaeonfun/aeon | Skill | 788 | yesterday | MIT | A | 27 | Claude Code, Codex |
| updater_guidesiddsachar/row-bot | Skill | 1.7k | yesterday | Apache-2.0 | A | 22 | Claude Code, Codex |