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/maintainnpx skills add slopus/happy --skill maintaingit 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.00053 | $0.01797 |
| Opus 5 | $0.00026 | $0.00898 |
| Sonnet 5 | $0.00011 | $0.00359 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
maintain 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 3d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/maintain - Open Source Project Maintenance
You are maintaining slopus/happy as an open source project. Every issue is a relationship with a user. Every close is a chance to build trust.
References (single source of truth - read these, don't inline)
- Contribution priorities:
docs/CONTRIBUTING.md - Roadmap themes:
docs/roadmap.md - Triage checkpoint (last session state, pending items, current
focus themes):
checkpoint.md
We do NOT use GitHub Projects, milestones, or priority/size fields.
Priorities and themes live in checkpoint.md.
Golden rule
NEVER close, comment on, merge, or modify issues/PRs without showing the exact text to the maintainer first and getting explicit approval. Even when told "close all" or "do X" - show the plan, get sign-off.
Double-confirmation on ALL human-facing actions
Any action that affects humans - closing issues, posting comments, merging PRs, editing issue text, labeling, assigning - requires explicit approval with the exact text/action shown first.
Feedback = still iterating. If the maintainer gives ANY feedback (questions, corrections, "but what about...", mixed responses), that means we are still thinking. Do NOT execute actions until feedback resolves into a clear, unambiguous directive. Specifically:
- Do NOT interpret "sure", "sounds good", listing numbers, or mixed feedback (act on some + questions on others) as blanket approval.
- After feedback is given, re-present the updated plan with exact text/messages that will be posted or executed.
- Wait for an explicit directive ("merge", "close these", "post it").
- If ambiguous, ask: "ready to execute?" - never assume.
PR merge rules
- CI must pass before merging. Never use
--adminto bypass branch protections. If CI hasn't run (first-time contributor), approve the workflow run first, wait for green, then merge. - Always show merge commit messages before merging. The maintainer must see and approve the exact message that lands in git history.
- Never batch-merge across feedback boundaries. If the maintainer gave feedback on 5 PRs and said "merge" on 2, only merge those 2. Re-present the others separately.
What ships with it
1 file 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.
- 3d ago First seen · 179 lines · 53 tokens per session scan A e90d683dbe5c
maintain is a skill published in the GitHub repository slopus/happy (23,553 stars, last pushed 5d ago), licensed MIT. It adds 53 tokens to every session and 1,797 once invoked, about $0.0003 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
issue-triage
Queries and triages open GitHub issues that need attention. Helps identify issues needing milestones, labels, or investigation.
gh-axi
Operate GitHub through the gh-axi CLI - issues, pull requests, workflow runs, workflows, releases, repositories, labels, Projects (v2), Actions secrets and variables, search, and raw API access. Use whenever a task touches GitHub: listing or filing issues, reviewing or merging PRs, checking CI runs, triggering…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
agentic-labeler
Labels issues and pull requests in the dotnet/maui repository with area- and platform/ labels ONLY, based on technical content and platform-file conventions. Used by the gh-aw agentic-labeler workflow and available for batch evaluation and interactive Copilot CLI usage.
azsdk-common-prepare-release-plan
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. UTILITY SKILL. USE FOR: "create release plan", "get release plan", "update release plan", "update API spec in release plan", "update SDK details in release plan", "abandon release plan", "link SDK PR to plan", "namespace…