Happy is a mobile, web, and desktop client that lets people use Claude Code and Codex remotely from their computers and mobile devices. It is for developers who want encrypted access to coding-agent sessions, including notifications and switching between devices. The catalogue add-ons extend the workflows available in this client.
Borrowing it
Nothing to install: this file belongs to slopus/happy. 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/slopus/happy/main/.agents/skills/maintain/SKILL.mdgit clone --depth 1 https://github.com/slopus/happyWrote 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/slopus/happy/maintain)<a href="https://agentmods.dev/skills/slopus/happy/maintain"><img src="https://agentmods.dev/badge/skills/slopus/happy/maintain/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/slopus/happy/maintain"><img src="https://agentmods.dev/badge/skills/slopus/happy/maintain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- 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.00053 | $0.01797 |
| Opus 5.5 | $0.00021 | $0.00719 |
| Sonnet 5.5 | $0.00011 | $0.00359 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
maintain 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/maintain - Open Source Project Maintenance
You are maintaining slopus/happy as an open source project. Every issue is a relationship with a user. Every close is a chance to build trust.
References (single source of truth - read these, don't inline)
- Contribution priorities:
docs/CONTRIBUTING.md - Roadmap themes:
docs/roadmap.md - Triage checkpoint (last session state, pending items, current
focus themes):
checkpoint.md
We do NOT use GitHub Projects, milestones, or priority/size fields.
Priorities and themes live in checkpoint.md.
Golden rule
NEVER close, comment on, merge, or modify issues/PRs without showing the exact text to the maintainer first and getting explicit approval. Even when told "close all" or "do X" - show the plan, get sign-off.
Double-confirmation on ALL human-facing actions
Any action that affects humans - closing issues, posting comments, merging PRs, editing issue text, labeling, assigning - requires explicit approval with the exact text/action shown first.
Feedback = still iterating. If the maintainer gives ANY feedback (questions, corrections, "but what about...", mixed responses), that means we are still thinking. Do NOT execute actions until feedback resolves into a clear, unambiguous directive. Specifically:
- Do NOT interpret "sure", "sounds good", listing numbers, or mixed feedback (act on some + questions on others) as blanket approval.
- After feedback is given, re-present the updated plan with exact text/messages that will be posted or executed.
- Wait for an explicit directive ("merge", "close these", "post it").
- If ambiguous, ask: "ready to execute?" - never assume.
PR merge rules
- CI must pass before merging. Never use
--adminto bypass branch protections. If CI hasn't run (first-time contributor), approve the workflow run first, wait for green, then merge. - Always show merge commit messages before merging. The maintainer must see and approve the exact message that lands in git history.
- Never batch-merge across feedback boundaries. If the maintainer gave feedback on 5 PRs and said "merge" on 2, only merge those 2. Re-present the others separately.
What ships with it
1 file 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.
- 1mo ago First seen · 179 lines · 53 tokens per session scan A e90d683dbe5c
maintain is a skill published in the GitHub repository slopus/happy (24,335 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,797 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
kanban-orchestrator
Kanban orchestrator: decompose, route, verify. No executing.
simply-pm
Use when you are spawned as the PM of a simply harness project and your brief references a .simply/LEDGER.md work ledger or this skill. Grants fleet authority, routing doctrine, safe worker lifecycle, and the signal protocol back to the auditor.
factory-update
Explains and drives the factory's update path — how improvements to the public template reach this office as a human-gated pull request. Invoke when the human asks 'is my factory up to date?', when a factory-update PR needs explaining hunk by hunk, or when an update was declined and needs a selective re-apply.
factory-retro
The factory learning to run itself better. Explicit-invoke: run when the human asks for a retro ('how are we doing?', 'what keeps going wrong?', '/factory-retro'), or on a schedule the human sets. Reads the journal end to end, finds friction patterns — repeated misses, slow handoffs, rules that keep tripping…
agency-chief-of-staff
A coordinator for complex, multi-stage projects that span conversations and tasks. It helps discuss requirements, create execution plans, assign roles, track progress, and preserve useful project knowledge.
agency-discuss-plan-execute-progress-archive
Discovery bridge for staged projects: discuss, plan, launch tasks, track progress, verify and archive. Excludes small tasks and source maintenance.