Borrowing it
Nothing to install: this file belongs to crystal-autobot/autobot. 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/crystal-autobot/autobot/main/.claude/skills/autobot-release/SKILL.mdgit clone --depth 1 https://github.com/crystal-autobot/autobotWrote 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/crystal-autobot/autobot/autobot-release)<a href="https://agentmods.dev/skills/crystal-autobot/autobot/autobot-release"><img src="https://agentmods.dev/badge/skills/crystal-autobot/autobot/autobot-release/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/crystal-autobot/autobot/autobot-release"><img src="https://agentmods.dev/badge/skills/crystal-autobot/autobot/autobot-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 19 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00019 | $0.00507 |
| Opus 5 | $0.00010 | $0.00253 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
autobot-release 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 12d 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
Release Workflow
Prerequisites
Ensure all checks pass before releasing:
crystal spec # All tests must pass
./bin/ameba # No warnings or failures
make release # Build must succeed
Version Bump
Follow Semantic Versioning (SemVer):
- MAJOR - Breaking changes (incompatible API changes)
- MINOR - New features (backward compatible)
- PATCH - Bug fixes (backward compatible)
Update version in:
shard.yml(Crystal standard)- Git tag
Git Commands
# 1. Update version in shard.yml
# 2. Commit version bump
git add shard.yml
git commit -m "chore(release): bump version to 1.2.3"
# 3. Create signed tag (requires GPG key)
git tag -s v1.2.3 -m "Release v1.2.3"
# 4. Push with tags
git push origin main --follow-tags
Conventional Commits
Use throughout development:
feat:- New featurefix:- Bug fixdocs:- Documentation onlystyle:- Formatting, missing semicolons, etc.refactor:- Code change that neither fixes bug nor adds featureperf:- Performance improvementtest:- Adding testschore:- Build process or auxiliary tool changes
Format:
type(scope): description
[optional body]
[optional footer]
GitHub Release
Create release via GitHub CLI:
gh release create v1.2.3 \
--title "Release v1.2.3" \
--verify-tag
Or manually:
- Go to GitHub Releases
- Click "Draft a new release"
- Choose the signed tag
- Add release notes
- Publish release
When to Use
Use this skill when:
- Preparing a new release
- Creating version tags
- Bumping version numbers
- Publishing to GitHub
Related Skills: autobot-test
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.
- 12d ago First seen · 96 lines · 19 tokens per session scan A 47b7681a5b5a
autobot-release is a skill published in the GitHub repository crystal-autobot/autobot (45 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 507 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
Release Readiness Reviewer
Reviews a release candidate and produces a go/no-go readiness decision.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
Release Checklist
Check release readiness and record a release note. Use for release and rollback requests.