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/alecs5am/ralphy/dev-releasenpx skills add alecs5am/ralphy --skill dev-releasegit clone --depth 1 https://github.com/alecs5am/ralphyWhat 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.00061 | $0.00765 |
| Opus 5 | $0.00030 | $0.00382 |
| Sonnet 5 | $0.00012 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00076 |
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.
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:
- GitHub Release with platform binaries and
SHA256SUMS. alecs5am/homebrew-tapformula.@alecs5am/ralphyon npm.
Never amend or replace an existing release. Never publish only one channel.
Procedure
-
Confirm the current branch is
main, the worktree is clean, andgh auth statusplusnpm whoamiidentify the expected maintainer. -
Read
scripts/release/last-release-commit, the latestv*tag, and commits since that baseline. Propose the semver bump and grouped release notes. -
Inspect the diff for public-doc impact. If needed, update
../ralphy-docs, validatedocs.json, commit, and push that repository separately. -
Run the CLI verification suite:
bun run lint bun test --timeout 45000 tests/unit tests/integration bun run build:bin:current gitleaks detect --source . -
After explicit user approval, update these version sources in lockstep:
package.jsoncli/lib/version.tsnpm/package.json- the current-version line in
AGENTS.md
-
Commit
chore(release): vX.Y.Z, tag that commitvX.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. -
Watch the GitHub Actions release workflow to success.
-
Run
scripts/release/update-brew-tap.sh vX.Y.Zandscripts/release/publish-npm.sh X.Y.Z, then verify both registries resolve the new version. -
Update
scripts/release/last-release-commitin a separate trailing commit so the next release has an exact baseline.
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 · 77 lines · 61 tokens per session scan A 46c54ee90d07
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.
Other skills, from other repositories
pr-explainer
Use when writing pull request descriptions, release notes, or summary diffs.
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.
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.
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…
deeptools
NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.
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.