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/agent-tower/core/publishnpx skills add agent-tower/core --skill publishgit clone --depth 1 https://github.com/agent-tower/coreWhat 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.00029 | $0.00723 |
| Opus 5 | $0.00015 | $0.00362 |
| Sonnet 5 | $0.00006 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
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 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.
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.
What it actually says
Publish to npm
流程
1. 版本号处理
- 读取
packages/server/package.json中的当前版本号 - 询问用户选择版本升级类型：
- patch (x.y.Z): bug 修复、小改动（默认）
- minor (x.Y.0): 新功能
- major (X.0.0): 破坏性变更
- 或用户直接指定版本号
- 更新
packages/server/package.json中的version字段 - 正式版从 prerelease 转正时去掉后缀，例如
0.5.4-beta.10→0.5.4 - 在构建前提交版本变更并保持工作区干净，保证 npm
gitHead可追溯
2. 构建
node scripts/build-publish.mjs
此脚本会：清理旧产物 → 构建 shared → server → web → 组装到 packages/server/publish/
Prisma 安装必须只有一个 Client 生成者。发布包捆绑 @prisma/client，但删除其中的 generate、postinstall 和可选 prisma peer；prisma CLI 作为与 Client 精确同版本的普通 dependency 安装，由 Agent Tower 根包的 postinstall 在目标机器生成本机 Client 和 engine。发布包还捆绑 @agent-tower/shared、包含多平台 prebuilds 的 @shitiandmw/node-pty，以及不含原生二进制和 postinstall 的 cloudflared JS 包装层；cloudflared 二进制由 server 在首次 Tunnel 启动时按目标平台下载。
3. 打包检查与冒烟
cd packages/server/publish
npm pack --dry-run
cd ../../..
pnpm publish:smoke
- 确认 tarball 包含已净化的
node_modules/@prisma/client，但不含node_modules/prisma、预生成的node_modules/.prisma或node_modules/cloudflared/bin pnpm publish:smoke必须从最终 tarball 做隔离全局安装，检查生成 Client 的语法、应用 Prisma 模块加载和 query engine- 验证首次 Tunnel 启动能安装目标平台 cloudflared
- 正式版发布前至少验证 macOS、Windows、Linux 的安装和 CLI 启动
4. 发布
cd packages/server/publish && npm publish --tag latest
beta 版本使用 npm publish --tag beta，不得依赖 npm 默认 tag。
5. 验证
发布成功后使用 npm view agent-tower dist-tags version --json 验证版本与 dist-tag，并告知用户新版本号。
注意事项
- 版本号冲突会返回 403，需升级版本号重试
- 禁止从含未提交源码改动的工作区发布
- 确保 npm 已登录（
npm whoami）
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 · 63 lines · 29 tokens per session scan A b5dcbd258cff
publish is a skill published in the GitHub repository agent-tower/core (341 stars, last pushed 22d ago), licensed Apache-2.0. It adds 29 tokens to every session and 723 once invoked, about $0.0001 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
new-changelog
Create the next desktop changelog entry when asked to add a changelog file or prepare the next release note under packages/changelog/content. Use this when the task is specifically about determining the next version and creating the markdown entry.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).