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-implement/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-implement)<a href="https://agentmods.dev/skills/happier-dev/happier/happier-implement"><img src="https://agentmods.dev/badge/skills/happier-dev/happier/happier-implement.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.00092 | $0.02996 |
| Opus 5 | $0.00046 | $0.01498 |
| Sonnet 5 | $0.00018 | $0.00599 |
| Haiku 4.5 | $0.00009 | $0.00300 |
Grade A, and why
happier-implement 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Happier Implement
Implement the requested outcome through the real owner and consumed runtime path. This skill owns the common change workflow; it does not create plans, authorize plan deviations, conduct a review-only program, or turn a diagnosis request into source edits.
1. Normalize the change and authority
Classify the requested work as a feature/change, bug fix, refactor/migration, mechanical transformation, or accepted review fix. Confirm that the user requested implementation rather than assessment, diagnosis, planning, or review only.
- For an approved plan, also use
.agents/skills/happier-implement-plan; that skill supplies the authoritative contract, execution units, state, and amendment rules. - For an accepted review finding, preserve the review's adjudicated impact and authority, then choose the coherent implementation rather than copying the reviewer's proposed mechanism blindly.
- For a runtime/session/provider/auth investigation without source changes, use
.agents/skills/happier-diagnose. - For read-only GitHub issue grouping or diagnosis, use
.agents/skills/happier-issue-triageand.agents/skills/happier-issue-diagnose. Enter this implementation workflow only after the user authorizes source changes, carrying forward the established issue evidence and version basis. - For a reported defect or regression, read bug-fix-loop.md before editing production behavior.
- When the repository constitution defines a successor-line obligation, include a destination disposition in the complete outcome. Work on and validate one coherent source batch first, then invoke the owning port workflow once at that boundary. Reuse current-basis diagnosis and port evidence, and revisit only changed intents unless scope, ownership, or architecture materially changed; do not port or reanalyze the destination during every source edit.
Do not create a repository plan on agent initiative. Use an internal checklist when useful, but keep it ephemeral unless an approved program already designates durable tracking.
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.
- yesterday Changed 071aef7a01aa
- 3d ago First seen · 138 lines · 92 tokens per session scan A 784c7a96af6b
happier-implement is a skill published in the GitHub repository happier-dev/happier (1,624 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 2,996 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
cmux-testing
A regression test for a bug fix ships as two commits so CI proves the test catches the bug.
testing-expert
Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices. Use when the user mentions TDD, BDD, unit tests, integration tests, or end-to-end tests, or when the task involves Testing Fundamentals, Unit Testing, Integration Testing, or End-to-End Testing.
absolute-work
End-to-end, phase-gated SDLC for AI coding agents: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge. Handles features, bugs, refactors, greenfield projects, planning breakdowns, and migrations. Triggers on "absolute work", "build this…
TDD 开发纪律助手
引导开发过程遵循测试先行、红绿重构和回归验证纪律。.
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
tdd
Test-driven development workflow for implementing features or fixing bugs through red-green-refactor. Use when the user asks to build, change, or fix behavior and the codebase has a practical automated test surface.