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/sessions/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/sessions)<a href="https://agentmods.dev/skills/slopus/happy/sessions"><img src="https://agentmods.dev/badge/skills/slopus/happy/sessions/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/sessions"><img src="https://agentmods.dev/badge/skills/slopus/happy/sessions.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.02869 |
| Opus 5.5 | $0.00031 | $0.01148 |
| Sonnet 5.5 | $0.00016 | $0.00574 |
| Haiku 4.5 | $0.00008 | $0.00287 |
Grade C, and why
sessions scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Capture the absolute path; thread it into Step 5 and Step 6. The OS handles cleanup on session end; an explicit `rm -rf "$SCRATCH"` at the end of Step 7 is harmless and makes intent explicit. Copies of this mod
1 near-identical copy found in the catalogue:
- ce:sessions — 95% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sessions (installed from EveryInc/compound-engineering-plugin ce-sessions)
Search session history across Claude Code, Codex, and Cursor and synthesize findings about what was worked on, tried, decided, or learned in prior sessions.
Usage
/ce-sessions [question or topic]
/ce-sessions
Pre-resolved context
Git branch (pre-resolved): !git rev-parse --abbrev-ref HEAD 2>/dev/null || true
If the line above resolved to a plain branch name (like feat/my-branch), use it for branch filtering and pass it to the synthesis subagent. If it still contains a backtick command string or is empty, derive the branch at runtime instead.
Repo name (pre-resolved): !basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || true
If the line above resolved to a plain repo folder name, use it for session discovery. Otherwise derive at runtime.
Note: 2026
The current year is 2026. Use this when interpreting session timestamps.
Guardrails
These rules apply at all times during orchestration and synthesis.
- Never read entire session files into context. Session files can be 1-7MB. Always use the extraction scripts to filter first, then reason over the filtered output.
- Never extract or reproduce tool call inputs/outputs verbatim. Summarize what was attempted and what happened.
- Never include thinking or reasoning block content. Claude Code thinking blocks are internal reasoning; Codex reasoning blocks are encrypted. Neither is actionable.
- Never analyze the current session. Its conversation history is already available to the caller.
- Surface technical content, not personal content. Sessions contain everything — credentials, frustration, half-formed opinions. Use judgment about what belongs in a technical summary and what doesn't.
- Fail fast on access errors. If session discovery fails on permissions, report the issue immediately. Do not retry the same operation with different tools or approaches — repeated retries waste tokens without changing the outcome.
What ships with it
4 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.
- 1mo ago First seen · 217 lines · 78 tokens per session scan C 6ad2164f6a5a
sessions is a skill published in the GitHub repository slopus/happy (24,335 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 2,869 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agentmailbox
Persistent context and inter-agent messaging across sessions and platforms. Activate when the user asks about resuming previous work, continuing where they left off, sharing context between agents, multi-agent coordination, remembering across sessions, cross-platform context sync, agent communication, or mailbox…
memory-layer
Three-tier memory layer for the orchestrator. Routes scratch (file-tier), WHERE (QMD), and WHY (MemPalace) through the existing code-memory-router slash command. Never edits planning files directly. Every WHY-tier promotion goes through the HITL gate.
session-handoff
Makes sessions durable across /clear, machine reboots, and IDE switches. SessionStart catchup pulls scratch + last MemPalace recall + planning files into context. Stop promotion writes a handoff note and runs memory-keeper. Manual /mddesign:handoff re-runs either at any time.
agentmailbox-cursor
Persistent context and inter-agent messaging for Cursor AI. Activate when the user asks about resuming previous work, continuing where they left off, sharing context between agents or tools, multi-agent coordination, remembering across Composer sessions, cross-platform context sync, or agent communication. Also…
agentmailbox-claude-code
Persistent context and inter-agent messaging for Claude Code CLI. Activate when the user asks about resuming previous work, continuing where they left off, sharing context between agents, multi-agent coordination, remembering across terminal sessions, or agent communication. Also activate on session start to check for…
wiki-ingest
Use when an operation issue asks to ingest a captured raw/ source into the LLM Wiki, or the user says "ingest ". Create durable source, entity, concept, synthesis, index, and log pages; use paperclip-distill for Paperclip bundles.