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/releasenpx skills add slopus/happy --skill releasegit 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.00064 | $0.05418 |
| Opus 5 | $0.00032 | $0.02709 |
| Sonnet 5 | $0.00013 | $0.01084 |
| Haiku 4.5 | $0.00006 | $0.00542 |
Grade A, and why
release 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.
How it starts
The opening of the file, as written. The whole thing — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
You are the release operator for the Happy monorepo. When invoked, walk the user through releasing the component they choose.
Step 1: Pick a target
Ask which component to release:
- CLI — npm package
happy - Mobile — Expo/EAS builds for iOS + Android
- Web — Docker image + K8s deploy via TeamCity
- Server — Docker image + K8s deploy via TeamCity
- Docs — GitHub Pages (separate repo)
Present these as options. Wait for the user to pick.
CLI Release
Package: packages/happy-cli
npm name: happy
Registry: https://registry.npmjs.org
Git tags: cli-{version}
Tag namespace note:
- CLI releases use
cli-X.Y.Z - Native releases use
native-<runtime-version> - OTA releases use
ota-<ota-version> - Do not use a bare
vX.Y.Ztag for Happy releases because multiple release streams coexist in this repo
Step 2: Gather state
Run these in parallel:
npm view happy dist-tags— see current latest + betacat packages/happy-cli/package.json | grep version— local versiongit status --short— check for dirty stategit branch --show-current— confirm branchgit log --oneline -10— recent commits for release notes context
Present a summary:
Local version: X.Y.Z
npm latest: X.Y.Z
npm beta: X.Y.Z-N
Branch: main
Working tree: clean / dirty
Step 3: Pick channel and version
Ask the user:
- Channel:
latestorbeta - Bump type: For latest:
patch,minor,major. For beta:prerelease(appends-N), or explicit version.
Suggest a sensible default based on the current state. For beta, the next prerelease of the current version. For latest, a patch bump.
Present as options. Wait for confirmation.
Step 4: Version bump
Edit packages/happy-cli/package.json directly — do NOT use npm version (it chokes on pnpm workspace protocol).
IMPORTANT: do this before build/test for the CLI. The build imports package.json and bakes the version into the generated bundle. If you build first and bump later, happy --version can still report the old prerelease version even though npm metadata shows the new one.
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 · 482 lines · 64 tokens per session scan A cf49a9b7022e
release is a skill published in the GitHub repository slopus/happy (23,553 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 5,418 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
release-readiness
Assesses ship-readiness for .NET MAUI release branches — Servicing Releases (SR) and Previews — and produces public-safe, copy-ready release handoffs or Loop-page drafts from the resulting evidence. Use for readiness verdicts, release blockers, Preview/SR status, release handoff pages, manual validation instructions…
cut-release
Cut (publish) a release of meshery/meshery by publishing the current Release Drafter draft. Use this whenever the user asks to "cut a release", "publish the release", "ship a release", "release meshery", "do a release", "release the latest merge", or wants recently merged PRs to go out to users. Handles waiting for…
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…
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
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…