happier: Skill for Codex

.agents/skills/happier-release-notes/SKILL.md

happier-release-notes is a skill for Codex from happier-dev/happier. It costs 34 tokens per session (1,116 once invoked), scanned A, original, MIT.

A workflow for validating and generating Happier release-note content, StoryDeck cards, translations, and related media assets from their canonical sources.

In plain words
What is it for?
Use it to check release-note schemas, create bounded channel text and cards, handle translations and assets, and generate the required outputs.
Why use it?
It keeps published projections consistent with the source files without asking the workflow to make editorial or release-policy decisions.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is happier-dev/happier's own configuration. It tells Codex how to work on happier itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything happier configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/pipeline/release/release-notes/project-release-notes.mjs \.

About the project

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.

happier-dev/happier · 1,624 stars · on GitHub · happier.dev

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/happier-dev/happier/dev/.agents/skills/happier-release-notes/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/happier-dev/happier

Made for: Codex.

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

agentmods badge for happier-release-notes

README.md
[![agentmods](https://agentmods.dev/badge/skills/happier-dev/happier/happier-release-notes.svg)](https://agentmods.dev/skills/happier-dev/happier/happier-release-notes)
Your own site
<a href="https://agentmods.dev/skills/happier-dev/happier/happier-release-notes"><img src="https://agentmods.dev/badge/skills/happier-dev/happier/happier-release-notes.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,116 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00034 $0.01116
Opus 5 $0.00017 $0.00558
Sonnet 5 $0.00007 $0.00223
Haiku 4.5 $0.00003 $0.00112

Measured 3d ago against content hash 3f102ae51165, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

happier-release-notes 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.

.agents/skills/happier-release-notes/SKILL.md · 123 lines

How it starts

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

Happier Release Notes

This skill owns only source-coupled release-note mechanics: the canonical changelog section schema, bounded-channel projection, StoryDeck cards, translations, assets, and generation. It does not choose release scope, group changes, write editorial prose, recommend patch/minor/major, approve content, or dispatch a release.

For those decisions, start with the private maintainer release authority:

hmaint release bootstrap --repo <absolute checkout> --json

Read first

  1. Read apps/ui/release-notes/README.md and apps/ui/release-notes/releases/README.md.
  2. Inspect apps/ui/sources/changelog/releaseNotes/types.ts and apps/ui/sources/components/ui/storyDeck/storyDeckCardLimits.ts before changing card data or limits.
  3. If UI behavior changes, use the canonical UI testkit and TDD.

Canonical changelog and bounded projections

apps/ui/CHANGELOG.md is the single authored authority for one release's public Markdown and exact bounded channel text. Put this JSON comment at the start of the matching ## Release <project-release-id> - <date> section. The project release ID is a unique lowercase identifier such as 2026-08-09.1, independent of every component version. Use the date plus an ordinal, increase the ordinal for another release on that date, and keep the same ID from preview through stable. The heading is the only authored source; a workflow input only selects and verifies it:

<!-- happier-release-note-projections:v1
{
  "expo": { "message": "Approved Expo text." },
  "appStore": { "whatsNew": "Approved App Store text." },
  "playStore": { "whatsNew": "Approved Play Store text." },
  "storyDeck": { "summary": "Approved StoryDeck text." }
}
-->

## Public heading

Approved public Markdown follows here.

The comment is removed from the GitHub/rolling Markdown projection. The script publishes every bounded string exactly as authored—there is no truncation, translation, synthesis, or AI rewrite. Expo is the currently consumed required projection. App Store, Play Store, and StoryDeck projections are optional until the selected release surfaces consume them; when present they are validated. Limits are: Expo 1,024; App Store 4,000; Play 500; StoryDeck 280. The section must contain meaningful public Markdown after the comment.

Read the full file on GitHub · 123 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago First seen · 123 lines · 34 tokens per session scan A 3f102ae51165

Subscribe to this mod's changes

happier-release-notes is a skill published in the GitHub repository happier-dev/happier (1,624 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 1,116 once invoked, about $0.0002 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.

Related

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.

BlockRunAI/ClawRouter · 44 tokens

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…

devoxx/DevoxxGenieIDEAPlugin · 121 tokens

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.

devoxx/DevoxxGenieIDEAPlugin · 64 tokens

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…

sonichi/sutando · 68 tokens

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.

manaflow-ai/cmux · 39 tokens

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.

openinterpreter/openinterpreter · 86 tokens