dev-release

A release procedure for the Ralphy command-line tool across GitHub Releases, Homebrew, and npm. A command-line tool is software operated from a terminal.

In plain words
What is it for?
Use it to check release prerequisites, prepare release notes, create the version tag, and publish the CLI with platform binaries, checksums, a Homebrew formula, and an npm package.
Why use it?
It keeps the tool’s version consistent across its distribution channels and prevents releasing only part of it.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/alecs5am/ralphy/dev-release
Any agent
npx skills add alecs5am/ralphy --skill dev-release
Clone the repo
git clone --depth 1 https://github.com/alecs5am/ralphy

Made for: Claude Code, Codex.

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 765 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00061 $0.00765
Opus 5 $0.00030 $0.00382
Sonnet 5 $0.00012 $0.00153
Haiku 4.5 $0.00006 $0.00076

Measured 2d ago against content hash 46c54ee90d07, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev-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 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.

.agents/skills/dev-release/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release the Ralphy CLI

This skill ships the agent-facing CLI in this repository. It never releases the marketing site, public docs site, desktop app, or unattended farm runtime.

Repositories

  • CLI: current repository, alecs5am/ralphy.
  • Public docs: sibling ../ralphy-docs, alecs5am/ralphy-docs.
  • Marketing and library: sibling ../ralphy-web, alecs5am/ralphy-web.
  • Desktop: sibling ../ralphy-desktop, alecs5am/ralphy-desktop.
  • Unattended automation: sibling ../ralphy-farm, alecs5am/ralphy-farm.

Only the CLI repository receives the vX.Y.Z release tag. If a CLI change affects public documentation, update and push ralphy-docs before tagging the CLI. Web, desktop, and farm changes follow their own release processes.

Release contract

One version must reach all three CLI channels:

  1. GitHub Release with platform binaries and SHA256SUMS.
  2. alecs5am/homebrew-tap formula.
  3. @alecs5am/ralphy on npm.

Never amend or replace an existing release. Never publish only one channel.

Procedure

  1. Confirm the current branch is main, the worktree is clean, and gh auth status plus npm whoami identify the expected maintainer.

  2. Read scripts/release/last-release-commit, the latest v* tag, and commits since that baseline. Propose the semver bump and grouped release notes.

  3. Inspect the diff for public-doc impact. If needed, update ../ralphy-docs, validate docs.json, commit, and push that repository separately.

  4. Run the CLI verification suite:

    bun run lint
    bun test --timeout 45000 tests/unit tests/integration
    bun run build:bin:current
    gitleaks detect --source .
    
  5. After explicit user approval, update these version sources in lockstep:

    • package.json
    • cli/lib/version.ts
    • npm/package.json
    • the current-version line in AGENTS.md
  6. Commit chore(release): vX.Y.Z, tag that commit vX.Y.Z, and push the commit and tag. Do not create the GitHub Release manually; the release workflow owns binaries, checksums, and the release object.

  7. Watch the GitHub Actions release workflow to success.

  8. Run scripts/release/update-brew-tap.sh vX.Y.Z and scripts/release/publish-npm.sh X.Y.Z, then verify both registries resolve the new version.

  9. Update scripts/release/last-release-commit in a separate trailing commit so the next release has an exact baseline.

Read the full file on GitHub · 77 lines

Changes

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.

  1. 2d ago First seen · 77 lines · 61 tokens per session scan A 46c54ee90d07

Subscribe to this mod's changes

dev-release is a skill published in the GitHub repository alecs5am/ralphy (128 stars, last pushed 7d ago), licensed Apache-2.0. It adds 61 tokens to every session and 765 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

pr-explainer

Use when writing pull request descriptions, release notes, or summary diffs.

imMamdouhaboammar/get-fable · 19 tokens

release

Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.

microsoft/agent-lightning · 63 tokens

gget

Fast CLI/Python queries to 20+ bioinformatics databases. Use for quick lookups: gene info, BLAST searches, AlphaFold structures, enrichment analysis. Best for interactive exploration, simple queries. For batch processing or advanced BLAST use biopython; for multi-database Python workflows use bioservices.

synthetic-sciences/openscience · 66 tokens

curated-bio-datasets

Guide to accessing curated biological datasets for computational biology. COSMIC cancer data, GTEx expression, GWAS catalog, GeneBass exome variants, BioGRID interactions, MSigDB gene sets, DisGeNET disease-gene associations, and GO ontology. For specific database APIs use individual database skills (cosmic-database…

synthetic-sciences/openscience · 79 tokens

deeptools

NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.

synthetic-sciences/openscience · 51 tokens

flow-cytometry-analysis

Complete flow cytometry analysis pipeline. FCS file handling, compensation, manual/automated gating, immunophenotyping, CFSE proliferation analysis, cell cycle analysis (Dean-Jett-Fox), and apoptosis assays. Extends flowio with analytical workflows. For raw FCS parsing only use flowio.

synthetic-sciences/openscience · 67 tokens