Happy is a mobile, web, and desktop client that lets people use Claude Code and Codex remotely from their computers and mobile devices. It is for developers who want encrypted access to coding-agent sessions, including notifications and switching between devices. The catalogue add-ons extend the workflows available in this client.
Borrowing it
Nothing to install: this file belongs to slopus/happy. 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/slopus/happy/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/slopus/happyWrote 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/slopus/happy/release)<a href="https://agentmods.dev/skills/slopus/happy/release"><img src="https://agentmods.dev/badge/skills/slopus/happy/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/slopus/happy/release"><img src="https://agentmods.dev/badge/skills/slopus/happy/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00064 | $0.06354 |
| Opus 5.5 | $0.00026 | $0.02542 |
| Sonnet 5.5 | $0.00013 | $0.01271 |
| Haiku 4.5 | $0.00006 | $0.00635 |
Grade A, and why
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 3d 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 — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
You are the release operator for the Happy monorepo. When invoked, walk the user through releasing the component they choose.
Step 0: Where you release from (never skipped)
Every release runs from a local main that is exactly origin/main, checked
against a fetch made right then. Not from a worktree. Not from a branch. Not
from a main that is ahead by an unpushed commit or behind by anyone else's.
Not with uncommitted changes. This applies to every target below: preview OTA,
production OTA, native builds, store submissions, CLI dispatch.
Why this is rule zero. On 2026-09-20 a preview OTA was published from a
worktree commit (fe7de0a1) that had branched off main hours earlier. The
commit was fine on its own, and it was later rebased and pushed, so git looked
right afterwards. But expo-updates serves whatever was published last on a
branch, not whatever is on main. For the next several hours every phone on
the preview channel ran a bundle missing four fixes that main already had:
bot faces, the truncated "Auto" chip, paste-from-clipboard, and the send button
being pushed out of the composer. Nothing errored. The user saw "the same old
issue" and could not tell why. A release from a stale checkout is not a
release, it is a rollback that nobody asked for.
Run this and read the output before any release command:
git checkout main
git fetch origin main
git rev-parse --abbrev-ref HEAD # must print exactly: main
git rev-parse HEAD origin/main # the two hashes must be identical
git status --porcelain # must print nothing
If HEAD is behind, git merge --ff-only origin/main. If it is ahead, the
commits are not on main yet — push first (see AGENTS.md "Sync To Main"),
then release. If the tree is dirty, commit or stash; a release must be
reproducible from the commit EAS records.
The mobile release scripts enforce this mechanically:
packages/happy-app/sources/scripts/releasePreflight.mjs runs first in ota,
ota:production, release:build:appstore, and the other release:build:*
scripts. It fetches, compares HEAD to origin/main, checks the tree is
clean, regenerates changelog.json and insists it is committed, and refuses
with the list of main commits the release would have dropped. If you run
eas update or eas build by hand instead of through those scripts, run the
preflight by hand first:
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.
- 3d ago Changed a46c696c8715
- 1mo ago Changed · +91 lines 0bf55f7570af
- 1mo ago Changed · -41 lines f131e5ea710b
- 1mo ago First seen · 482 lines · 64 tokens per session scan A cf49a9b7022e
release is a skill published in the GitHub repository slopus/happy (24,335 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 6,354 once invoked, about $0.0003 per session on Opus 5.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
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.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
github
Skill "github" from Hmbown/Codewhale, covering github, when to use, setup, workflow and non-goals.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.