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 instructions/hitosea/happy-next/claude-mdgit clone --depth 1 https://github.com/hitosea/happy-nextWrote 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/instructions/hitosea/happy-next/claude-md)<a href="https://agentmods.dev/instructions/hitosea/happy-next/claude-md"><img src="https://agentmods.dev/badge/instructions/hitosea/happy-next/claude-md.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 | $0.00283 | $0.00283 |
| Opus 5 | $0.00142 | $0.00142 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
happy-next CLAUDE.md 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 5d 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.
What it actually says
Interaction Rules
- Always suggest options when asking questions — when clarifying requirements, provide concrete recommendations or choices to help the user decide quickly, rather than open-ended questions
Language Preference
- Respond in Simplified Chinese unless the user explicitly requests another language
Repository Overview
Yarn 1.x monorepo ([email protected]).
| Package | Purpose |
|---|---|
| happy-app | Expo/React Native mobile + web client |
| happy-cli | CLI wrapper for Claude Code, Codex, Gemini |
| happy-server | Fastify backend (API + Socket.IO) |
| happy-voice | LiveKit-based voice gateway |
| happy-wire | Shared Zod schemas and wire types |
Type Checking (run after all changes)
Run yarn typecheck in the package you modified. In happy-server the command is yarn build (which is tsc --noEmit, not a real build step).
happy-wire (run after every change)
After modifying the happy-wire package, always run yarn build in it — consumers depend on its compiled dist output, so changes won't take effect until rebuilt.
Running a Single Test (Vitest)
npx vitest run path/to/file.test.ts
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.
- 5d ago First seen · 34 lines · 283 tokens per session scan A 0121b21d7d15
happy-next CLAUDE.md is an instructions file published in the GitHub repository hitosea/happy-next (59 stars, last pushed yesterday), licensed MIT. It adds 283 tokens to every session, about $0.0014 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).