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/longbkit/clisbot/release-clisbotnpx skills add longbkit/clisbot --skill release-clisbotgit clone --depth 1 https://github.com/longbkit/clisbotWhat 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.00074 | $0.01098 |
| Opus 5 | $0.00037 | $0.00549 |
| Sonnet 5 | $0.00015 | $0.00220 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
release-clisbot 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Clisbot
Use this skill from the current clisbot checkout. Do not assume or record a
machine-specific absolute path; verify the repo root by finding package.json
with package name clisbot and the repo AGENTS.md.
Hard Rules
- Run
npm loginandnpm publish --access publicin an attached session. - If npm returns a browser approval URL, send that exact URL to the operator and continue the same attached session after approval.
- Never use
npm publish --otp,npm login --otp, or any OTP fallback. - If npm returns
EOTPor demands OTP instead of browser approval, stop and ask; do not invent a manual OTP path. - Do not publish until version, docs, release notes, migration decision, gates, and package dry-run are aligned.
- If any release path, version, tag, or migration requirement is unclear, ask before publishing.
- Do not include local machine paths in release notes, GitHub Releases, or skill reports unless the operator explicitly asks for a local filesystem path.
Preflight
-
Start from the current checkout root, not a hard-coded path:
test "$(node -p "require('./package.json').name")" = "clisbot" -
Read
AGENTS.mdanddocs/development/README.md. -
Inspect
git status --short,package.json,CHANGELOG.md,docs/releases/README.md,docs/releases/upcoming.md,docs/migrations/index.md, and the latestdocs/updates/releases/*-release-guide.md. -
Decide the release lane: first beta, next beta, or official stable/latest.
-
Confirm there are no unrelated uncommitted changes that should be excluded from the release.
-
If publishing is requested, confirm npm auth with
npm whoamiafternpm loginwhen auth may be stale.
Version Lanes
Use SemVer prerelease syntax with a hyphen.
X.Y.Z-beta.1 < X.Y.Z-beta.2 < X.Y.Z
First beta:
VERSION=X.Y.Z-beta.1
npm version "$VERSION" --no-git-tag-version
npm login
npm publish --access public --tag beta
npm view clisbot@beta version
npm view clisbot dist-tags
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 115 lines · 74 tokens per session scan A 61d15e38acd1
release-clisbot is a skill published in the GitHub repository longbkit/clisbot (114 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 1,098 once invoked, about $0.0004 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
chatbot
Use when a support or sales bot on a live website must behave: persona/system prompt, grounding so it cannot invent prices or policy, jailbreak and injection defense, the human handoff, launch metrics and kill switch. NOT the agent loop or RAG index under it (that is building-agents), NOT a human answering one ticket…
create-ppt
Creates polished PowerPoint presentations with dark-first design, custom palettes, charts, and tables. Use when creating, designing, or generating PPTX slide decks or presentations.
create-pdf
Guidelines for creating polished, themed PDF reports with the code execution tool.
skill-authoring-best-practices
Best practices for writing effective Skills that are discoverable, concise, and reliable. Use when creating, reviewing, or improving Skills.
cloud_storage
Skill for uploading and downloading files from cloud storage (AWS S3 or Azure Blob Storage).
sandbox_file_manager
Use this skill when you need to manage files inside the active remote or local sandbox, including listing sandbox files, downloading files from the sandbox to the local backend, or uploading local backend files to the sandbox.