happier-docs

happier-docs is a skill for Claude Code, Codex from happier-dev/happier. It costs 78 tokens per session (2,079 once invoked), scanned A, original, MIT.

A guide for creating, updating, organizing, and reviewing Happier’s internal and published technical documentation.

In plain words
What is it for?
Use it for architecture notes, user and operator guides, contributor documentation, troubleshooting pages, and documentation reviews.
Why use it?
It keeps documentation accurate, current, appropriately placed, and matched to the people who use it.

Skill for Claude CodeCodex

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,619 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/happier-dev/happier/happier-docs
Any agent
npx skills add happier-dev/happier --skill happier-docs
Clone the repo
git clone --depth 1 https://github.com/happier-dev/happier

Made for: Claude Code, 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-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/happier-dev/happier/happier-docs.svg)](https://agentmods.dev/skills/happier-dev/happier/happier-docs)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,079 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00078 $0.02079
Opus 5 $0.00039 $0.01040
Sonnet 5 $0.00016 $0.00416
Haiku 4.5 $0.00008 $0.00208

Measured today against content hash 36e40c43ee6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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-docs/SKILL.md · 108 lines

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.

Read the full file on GitHub · 108 lines

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. today Changed 36e40c43ee6c
  2. 2d ago First seen · 108 lines · 78 tokens per session scan A b34adb536da2

Subscribe to this mod's changes

happier-docs is a skill published in the GitHub repository happier-dev/happier (1,619 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 2,079 once invoked, about $0.0004 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

determinism-audit

Audits nondeterministic game behavior and flaky execution. Use when the same initial state and inputs produce different outcomes, a test fails intermittently or only under load, behavior differs by frame rate or machine, a replay diverges, or lockstep peers desynchronize. Establishes the required determinism boundary…

NEXPACE-Limited/msu-skills · 107 tokens

maple-preview

Use when a MapleStory asset request resolves to more than one plausible candidate: a look described by colour, style, or mood instead of an exact name or ID (a black cap, a white tee, a monster that suits this map), a maple-lookup search returning several close matches, or the user asking to preview, compare, or…

NEXPACE-Limited/msu-skills · 101 tokens

audio-check

Checks, repairs, or sets up a browser game's audio: its sound settings and whether sound actually plays under each browser's conditions. Use when a game is silent, or goes silent, on a phone, in Safari, inside an iframe or an in-app browser while it plays elsewhere; when sound works for the builder but not for…

NEXPACE-Limited/msu-skills · 146 tokens

balance-tuning

Reviews and tunes game balance across difficulty and progression curves, session pacing, option or strategy trade-offs, and reward economies. Use when players report that a game is too hard, easy, short, long, or grindy; a weapon, upgrade, or strategy dominates; damage, health, spawn, drop, price, or progression…

NEXPACE-Limited/msu-skills · 110 tokens

cross-device-check

Audits a game's UI and interaction across supported viewports, aspect ratios, pixel densities, orientations, and input capabilities. Use when mobile, tablet, desktop, controller, keyboard, pointer, or touch support is being checked; UI clips, overlaps, blurs, or overflows; controls are unreachable or hard to use…

NEXPACE-Limited/msu-skills · 118 tokens

game-feel

Use when a game's controls feel stiff, floaty, heavy, slippery, unresponsive, or unfair; when players miss jumps they thought they made, snag on platform corners, lose inputs pressed during another action, or get hit by grazes; when a platformer, runner, or action game is being built or polished and its input and…

NEXPACE-Limited/msu-skills · 127 tokens