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-docs/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-docs)<a href="https://agentmods.dev/skills/happier-dev/happier/happier-docs"><img src="https://agentmods.dev/badge/skills/happier-dev/happier/happier-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/happier-dev/happier/happier-docs"><img src="https://agentmods.dev/badge/skills/happier-dev/happier/happier-docs.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.02079 |
| Opus 5.5 | $0.00031 | $0.00832 |
| Sonnet 5.5 | $0.00016 | $0.00416 |
| Haiku 4.5 | $0.00008 | $0.00208 |
Grade A, and why
happier-docs 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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Happier Documentation
Keep documentation truthful, useful, current, and owned without turning every code change into prose churn. Follow the root constitution and, for published docs, apps/docs/AGENTS.md. For an explicit deep review or QA request, use .agents/skills/happier-review as the orchestrator and apply this skill as the documentation-domain standard; this skill does not create a competing general review workflow.
1. Classify the documentation impact
For the changed behavior or contract, decide whether it affects:
- internal technical/product architecture under
docs/**; - published user/operator/self-hoster/contributor behavior under
apps/docs/content/docs/**; - both surfaces;
- neither surface, with a concrete reason.
A refactor that leaves every documented contract unchanged may need no docs edit. A behavior, command, setting, support status, workflow, failure/recovery path, protocol, persistence shape, compatibility rule, deployment requirement, or canonical owner change normally does.
2. Identify audience, page type, and canonical owner
Classify published pages as task guide, concept, reference, troubleshooting, or development documentation. Internal docs explain architecture, contracts, ownership, and contributor-facing implementation constraints.
Search by the feature, command, setting, route, schema, provider/agent id, UI label, error, and reader phrasing before creating a page. Update, move, consolidate, or retire the canonical page instead of adding a parallel explanation. Map links, navigation, related pages, examples, and translations or screenshots that depend on the changed documentation contract.
Placement is part of authorship, not cleanup afterwards. A published page belongs to exactly one section, is listed in that section's meta.json at the point a reader should meet it, and is linked from that section's index.mdx. A page missing from either is unreachable in a way that breaks no link and shows up in no diff. Moving a page is the same four edits in reverse. The section inventory is in apps/docs/AGENTS.md.
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.
- 1mo ago Changed 36e40c43ee6c
- 1mo ago First seen · 108 lines · 78 tokens per session scan A b34adb536da2
happier-docs is a skill published in the GitHub repository happier-dev/happier (2,072 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 2,079 once invoked, about $0.0003 per session on Opus 5.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
agtx-oneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each one. Use when the user wants a long autonomous run rather than a single session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
agtx-execute
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
agtx-plan
Plan a task implementation. Analyze the codebase, create a detailed plan, write it to .agtx/plan.md, then stop and wait for user approval before making any changes.
agtx-research
Explore the codebase to understand a task before planning. Write findings to .agtx/research.md and stop. This is a read-only exploration — do not modify any files.
agtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.