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/corespeed-io/wechatbot/publishnpx skills add corespeed-io/wechatbot --skill publishgit 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.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00018 | $0.01019 |
| Sonnet 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 6d 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.
- 6d ago First seen · 206 lines · 37 tokens per session scan A 166df7c1fc74
publish is a skill published in the GitHub repository corespeed-io/wechatbot (630 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 2,039 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-30.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…