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-review/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-review)<a href="https://agentmods.dev/skills/happier-dev/happier/happier-review"><img src="https://agentmods.dev/badge/skills/happier-dev/happier/happier-review.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.00113 | $0.03542 |
| Opus 5 | $0.00056 | $0.01771 |
| Sonnet 5 | $0.00023 | $0.00708 |
| Haiku 4.5 | $0.00011 | $0.00354 |
Grade A, and why
happier-review 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 yesterday.
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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Happier Review
Use this as the only general review orchestrator for Happier. The superseded generic review-protocol and code-reviewer skills are archived and must not be invoked here; this skill absorbs their useful review categories and routes to the narrower repository skills that own testing, compatibility, diagnosis, and verification.
1. Normalize the request
Determine five independent values before reviewing:
- Target — session, worktree, plan, feature/corridor, commit, branch/PR, bounded codebase, or release validation.
- Intent basis — user request, plan, issue, PR description, ADR, or documented contract.
- Output mode —
report,comment,qa,staged, orfix. - QA surfaces — automated, browser, device, CLI/API/daemon, persistence/compatibility, platform, or release.
- Review class —
advisory,boundary, orship.
Infer these from clear wording; ask only when the wrong target/base/mode would materially change the work or authorize writes the user did not request. Read targets.md for target inference and mixed dirty-worktree attribution. For plan targets or plan-backed reviews, identify whether the plan is a draft under pre-approval review or an approved execution contract, then read plan-completeness.md. Do not turn an implementation-completeness audit into a second plan-design review.
Mode rules:
report: review and QA only; recommendations, no source/config/test edits.comment: same as report, with concise PR-style comments backed by the full evidence record.qa: exercise the requested behavior and investigate failures without source edits or a general code-review mandate.staged: finish and present the reviewed finding/fix set, then wait for approval before source edits.fix: review, triage, implement authorized root-cause fixes, validate, and re-review.
If the request contains several example prompts with different modes, treat them as examples. Follow the user's actual requested deliverable; do not merge contradictory example clauses into one execution mode.
What ships with it
12 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.
- agents/openai.yaml 243 B
- assets/LANE.md 877 B
- assets/REPORT.md 411 B
- assets/TRACKING.md 1.7 KB
- references/orchestration.md 7.4 KB
- references/output-modes.md 3.9 KB
- references/plan-completeness.md 8.1 KB
- references/qa-coverage.md 8.6 KB
- references/review-standard.md 12 KB
- references/targets.md 4.1 KB
- references/tracking-and-evidence.md 3.6 KB
- scripts/bootstrap-review.mjs 5.2 KB runs code
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.
- yesterday Changed 84f5fc79a6d7
- 3d ago First seen · 205 lines · 113 tokens per session scan A 5845f84f45cf
happier-review is a skill published in the GitHub repository happier-dev/happier (1,624 stars, last pushed yesterday), licensed MIT. It adds 113 tokens to every session and 3,542 once invoked, about $0.0006 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.
ccmanager-config
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global /.config/ccmanager/config.json. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree…
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…