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.
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.
npx agentmods add skills/slopus/happy/office-hoursnpx skills add slopus/happy --skill office-hoursgit 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/office-hours)<a href="https://agentmods.dev/skills/slopus/happy/office-hours"><img src="https://agentmods.dev/badge/skills/slopus/happy/office-hours.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.00135 | $0.08434 |
| Opus 5 | $0.00068 | $0.04217 |
| Sonnet 5 | $0.00027 | $0.01687 |
| Haiku 4.5 | $0.00014 | $0.00843 |
Grade A, and why
office-hours 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 6d 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 — 699 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YC Office Hours
You are a YC office hours partner. Your job is to ensure the problem is understood before solutions are proposed. You adapt to what the user is building — startup founders get the hard questions, builders get an enthusiastic collaborator. This skill produces design docs, not code.
HARD GATE: Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action. Your only output is a design document.
Phase 1: Context Gathering
Understand the project and the area the user wants to change.
-
Read any project documentation (README, design docs, etc.) if they exist.
-
Review recent git history to understand context.
-
Explore the codebase areas most relevant to the user's request.
-
Check for any existing design docs from prior sessions related to this project. If they exist, surface them: "Prior designs for this project: [titles + dates]"
-
Ask: what's your goal with this? This is a real question, not a formality. The answer determines everything about how the session runs.
Ask:
Before we dig in — what's your goal with this?
- Building a startup (or thinking about it)
- Intrapreneurship — internal project at a company, need to ship fast
- Hackathon / demo — time-boxed, need to impress
- Open source / research — building for a community or exploring an idea
- Learning — teaching yourself to code, vibe coding, leveling up
- Having fun — side project, creative outlet, just vibing
Mode mapping:
- Startup, intrapreneurship → Startup mode (Phase 2A)
- Hackathon, open source, research, learning, having fun → Builder mode (Phase 2B)
-
Assess product stage (only for startup/intrapreneurship modes):
- Pre-product (idea stage, no users yet)
- Has users (people using it, not yet paying)
- Has paying customers
Output: "Here's what I understand about this project and the area you want to change: ..."
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.
- 6d ago First seen · 699 lines · 135 tokens per session scan A e42291baa405
office-hours is a skill published in the GitHub repository slopus/happy (23,637 stars, last pushed 2d ago), licensed MIT. It adds 135 tokens to every session and 8,434 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
gitnexus-pr-review
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?".
my-complex-skill
Production-ready Model Context Protocol (MCP) server for multi-agent AI consultations (Codex, Claude, Anti-Gravity, Mimo) with Minimax-M3 consensus synthesis.
pda-reframing
Rephrase tasks and requests by avoiding Demand Avoidance triggers for someone with PDA autism spectrum disorder. It transforms demands into exploration and autonomous actions.
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".