Happier is an open-source, end-to-end encrypted client that lets people run AI coding-agent sessions on a computer and continue controlling them from a phone, browser, or desktop app. It is for developers who use agents such as Claude Code, Codex, Gemini, or OpenCode across multiple devices, with self-hosting available. The catalogue entries are add-ons for configuring or extending this client and its supported coding-agent workflows.
Borrowing it
Nothing to install: this file belongs to happier-dev/happier. 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/happier-dev/happier/dev/.agents/skills/happier-release-validation/SKILL.mdgit clone --depth 1 https://github.com/happier-dev/happierWrote 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/happier-dev/happier/happier-release-validation)<a href="https://agentmods.dev/skills/happier-dev/happier/happier-release-validation"><img src="https://agentmods.dev/badge/skills/happier-dev/happier/happier-release-validation.svg" alt="Measured on agentmods" height="20"></a>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.00025 | $0.00717 |
| Opus 5 | $0.00013 | $0.00358 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
happier-release-validation 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Happier Release Validation
This is the repository-owned entrypoint for the public release contract's
manual-only deep profile. It does not publish, promote, deploy, submit stores,
or create a release operation.
Start from the target contract
From the explicit release checkout, inspect the target-owned profile and its executable suite inventory:
node scripts/pipeline/run.mjs release-contract
node scripts/pipeline/run.mjs release-validate --profile deep --dry-run
deep is not part of normal release dispatch. This skill is its manual
entrypoint; the registry does not pretend that semantic compatibility or human
QA can be decided by a script.
For general release preparation or approval, first use the installed private maintainer authority:
hmaint release bootstrap --repo <absolute checkout> --json
Read and follow the returned private skill for general release preparation or approval. This repository skill remains the target-owned deep-certification entrypoint only.
If hmaint is unavailable, stop and obtain the approved maintainer-tool
installation; do not substitute a copied release workflow or arbitrary shell
commands.
Manual certification
- Record the release source SHA and every independently versioned component changed by that source. Resolve supported stable/preview baselines to immutable tags/artifacts; a rolling tag is discovery only.
- Read
docs/compatibility.md, map only reachable old/new directions, and perform the target-owned suite commands for affected automatic-capable surfaces. Record unrun or unavailable proof as such. - Use the non-mutating
deepprofile intests-dispatch.ymlfor complete in-repository source certification. Run credentialed live-provider scenarios separately through their explicit provider-contract entrypoint when the affected surface requires them. Native/store publication is release work, not certification, and must not be invoked from this skill. Keep editorial judgement, release-note wording, and subjective compatibility assessment human-reviewed; do not encode them as prose/style tests. - For every manual scenario, preserve practical evidence: source/baseline identity, command or observed user flow, result, and recovery/failure state. Use an existing release record when one exists; do not create a parallel ledger, lifecycle state, or certification authority.
- Report passed, failed, skipped, and blocked checks to the maintainer. A manual certification is evidence for human approval, never the approval itself.
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 First seen · 78 lines · 25 tokens per session scan A 5401a06c009c
happier-release-validation is a skill published in the GitHub repository happier-dev/happier (1,624 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 717 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-09-03.
Other skills, from other repositories
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
release
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
release
Prepare, verify, and publish Sutando engine releases. Use when asked to prepare a release proposal, determine a version bump, audit release documentation, validate release gates, create a release PR, tag a confirmed release, or publish GitHub release notes. Preparation is safe and non-publishing; tagging and…
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers commits since the last tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.