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/slopus/happy/agents-mdgit clone --depth 1 https://github.com/slopus/happyWhat 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.00082 | $0.00082 |
| Opus 5 | $0.00041 | $0.00041 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
happy AGENTS.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 2d 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
Agent Workflow
Sync To Main
When the user says sync to main or synt to main, they mean:
- Fetch
origin/main. - Rebase the current branch on
origin/main. - Push the current HEAD directly to
mainwith a normal push, for example:git push origin HEAD:main
Do not force push for this workflow.
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.
- 2d ago First seen · 13 lines · 82 tokens per session scan A 450a37c7efe1
happy AGENTS.md is an instructions file published in the GitHub repository slopus/happy (23,553 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session, 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-08-30.
Other instructions, from other repositories
ai-context-hierarchy CLAUDE.md
Instructions for CreatmanCEO/ai-context-hierarchy, covering ai-context-hierarchy — claude.md (level 1), status: active, architecture, critical rules — when editing this repo and commands.
agent-consult CLAUDE.md
Claude Code instructions for VKirill/agent-consult, covering agent consult — claude code guidelines, build and test commands, system guidelines and gitnexus, gitnexus — code intelligence and always do.
agent-consult AGENTS.md
AGENTS.md instructions for VKirill/agent-consult, covering gitnexus — code intelligence, always do, never do, resources and cli.
ASD-AuDHD-PAI-Skills CLAUDE.md
Instructions for emory/ASD-AuDHD-PAI-Skills: You are the personal AI infrastructure of your user and this repository contains some Claude Skills that are intended to be used by someone that cares for or works with people with so-called "AuDHD" (ADHD+ASD), or other manifestation of pathological demand avoidance.
driftguard-mcp CLAUDE.md
Claude Code instructions for jschoemaker/driftguard-mcp, covering driftcli — project context, what it is, architecture, file map and the 7 drift factors.
apm python.instructions.md
Python development guidelines.