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-pr-steward/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-pr-steward)<a href="https://agentmods.dev/skills/happier-dev/happier/happier-pr-steward"><img src="https://agentmods.dev/badge/skills/happier-dev/happier/happier-pr-steward.svg" alt="Measured on agentmods" height="20"></a>- 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.00106 | $0.02032 |
| Opus 5 | $0.00053 | $0.01016 |
| Sonnet 5 | $0.00021 | $0.00406 |
| Haiku 4.5 | $0.00011 | $0.00203 |
Grade A, and why
happier-pr-steward 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Happier PR Steward
Own the PR lifecycle and its human gates. Delegate the actual review standard, implementation, testing, compatibility analysis, commit safety, and GitHub mutations to their canonical skills instead of duplicating them here.
1. Load the owning workflows
Use these skills as applicable:
.agents/skills/happier-reviewfor the review basis, affected corridor, findings, and merge assessment;.agents/skills/happier-implementand.agents/skills/happier-testingfor approved behavior changes and RED -> GREEN evidence;.agents/skills/happier-compatibilityfor released seams and version skew;.agents/skills/happier-port-0-2-to-0-3when a 0.2 PR must be represented in the 0.3 line;.agents/skills/happier-commit-worktreewhen a destination checkout is large or actively dirty;.agents/skills/happier-github-opsfor authenticated GitHub reads and every public mutation;.agents/skills/verify-claimsbefore relying on bot, human, CI, or delegated claims;.agents/skills/attack-conclusionand.agents/skills/handoff-reportfor closeout.
Read lifecycle.md before starting.
2. Establish the live basis
Treat the PR body, patch, reviews, comments, approvals, and check results as claims. Fetch the current base and head SHAs, author identity, commits, complete diff, changed files, discussion, review threads, and checks. Record the head SHA for every analysis and re-check it before acting on a result.
Use a separate worktree for a foreign PR branch when needed. Never switch the primary checkout, discard local bytes, trust inherited staging, or mix unrelated work into a PR commit.
Inventory material contribution rather than using PR authorship as an attribution shortcut. For each planned commit, identify whose code, patch, design, causal diagnosis, decisive reproduction, or substantially adopted fix direction that commit actually incorporates. Resolve and add a verified Co-authored-by: trailer for each such contributor. The PR author normally earns co-authorship on commits that preserve or refactor their contributed code/intent, but not on independent steward fixes merely because they opened the PR. A newly derived fix for a reviewer finding does not transfer co-authorship to the PR author, and an automated reviewer does not create a human co-author claim. Review comments, participation, generic suggestions, requested logs, and confirmation alone do not qualify. Evaluate every commit independently, acknowledge useful non-qualifying help publicly, and stop before a commit only when a material contributor's required identity cannot be verified; never guess or expose an email.
What ships with it
2 files 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.
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 459588a0eff0
- 5d ago First seen · 101 lines · 106 tokens per session scan A 6f1c1ba18d5f
happier-pr-steward is a skill published in the GitHub repository happier-dev/happier (1,638 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 2,032 once invoked, about $0.0005 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
review-preflight
Review tooling for a PR: review-preflight prints REVIEW.md's criteria and the PR's live gate state before a review; ci-triage maps a PR's failing checks to already-filed issues.
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
kimi-swarm-write
Run a write-capable Kimi swarm that edits many disjoint targets in a throwaway worktree and returns a reviewable patch. Use only for explicit parallel edit fan-out requests; the plugin never applies or commits the patch.
ship-pr
Ship one pull request, monitor hosted CI and review feedback, follow PR policy, and request authorization before merging and cleaning up.
lrc
Manage LiveReview code review for staged changes in this repo. Run /lrc review to open a browser-based AI review of staged changes before committing. Use /lrc skip to bypass review and write an attestation, or /lrc vouch to manually approve without AI. Check and toggle hook state with /lrc hooks status, hooks disable…
glab-mr
A command-line tool for creating, reviewing, approving, discussing, and merging GitLab merge requests. A merge request is a proposed set of code changes for others to inspect before it is added to a project.