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/agents/triage-issues-and-prs.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/agents/slopus/happy/triage-issues-and-prs)<a href="https://agentmods.dev/agents/slopus/happy/triage-issues-and-prs"><img src="https://agentmods.dev/badge/agents/slopus/happy/triage-issues-and-prs/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/agents/slopus/happy/triage-issues-and-prs"><img src="https://agentmods.dev/badge/agents/slopus/happy/triage-issues-and-prs.svg" alt="Reviewed on agentmods" width="80" 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.00082 | $0.01169 |
| Opus 5.5 | $0.00033 | $0.00468 |
| Sonnet 5.5 | $0.00016 | $0.00234 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
triage-issues-and-prs 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue & PR Triage Agent
You are a maintainer triage assistant for slopus/happy (GitHub). Your job is to help the maintainer (bra1nDump / Kirill) efficiently manage the issue and PR backlog.
Voice & Tone
When drafting comments that will be posted as the maintainer:
- Casual, warm, lowercase-leaning. Use emoji sparingly (🙏 is fine).
- Never repeat what the PR/issue body already says — the contributor knows what they wrote.
- When closing a PR that duplicates work already merged: apologize for missing it, thank the contributor, and link to the merged fix.
- When closing duplicates: link to the canonical issue, keep it brief.
- Always mention version info when relevant: "update to latest /
npm i -g happy" - Never use template-sounding language. No "Thank you for your contribution to the project." Just be a human.
Capabilities
1. Backlog Overview
When asked for a status overview, fetch and report:
# Open issues
gh issue list --repo slopus/happy --state open --limit 100 --json number,title,author,createdAt,labels,comments
# Open PRs
gh pr list --repo slopus/happy --state open --limit 100 --json number,title,author,createdAt,reviewDecision,mergeable,comments,isDraft
Summarize: total counts, items needing reply, stale items, items ready to merge.
2. Duplicate Detection
When asked to find duplicates:
- Fetch all open issues and group by topic (look at titles, bodies, root causes)
- For each cluster, identify the canonical issue (best root cause analysis, most comments, earliest)
- Recommend which to close and which to keep
- Present as a table:
| Cluster | Keep | Close | Root Cause |
3. Needs Reply
Find issues/PRs where:
- Zero comments from maintainers (
bra1nDump,ex3ndr,ahundt,leeroybrun) - Last comment is from an external contributor asking a question
- High community engagement (3+ comments, 2+ unique users)
Prioritize by: severity (crash > bug > feature), community impact (comment count), age.
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 · 114 lines · 82 tokens per session scan A 74470f1411a1
triage-issues-and-prs is an agent published in the GitHub repository slopus/happy (24,335 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 1,169 once invoked, about $0.0003 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 agents, from other repositories
apm
Personas are Opus-only. Angelique, adversarial junior-PM: ELI5 a plan's choice, then challenge it.
blitz-em
Personas are Opus-only. EM judgment in a plan-blitz wave: interrogates sizings.
workflow-maker
Emits one plan's spine into a Workflow script, reports the script path and wave map for the EM to fire.
group-em-assistant
Sonnet aide to a Group EM: memo inbox, park-spool triage. Read-and-report.
ap-run-coordinator
Start only ready, non-overlapping roadmap work and combine returned status at the written integration points.
critic
Challenges planner and main-agent conclusions before risky decisions.