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-agent/release-agentnpx skills add slopus/happy-agent --skill release-agentgit clone --depth 1 https://github.com/slopus/happy-agentWrote 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/skills/slopus/happy-agent/release-agent)<a href="https://agentmods.dev/skills/slopus/happy-agent/release-agent"><img src="https://agentmods.dev/badge/skills/slopus/happy-agent/release-agent.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.00062 | $0.01714 |
| Opus 5 | $0.00031 | $0.00857 |
| Sonnet 5 | $0.00012 | $0.00343 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
release-agent 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 4d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing Happy Agent
Releases go out through GitHub Actions using trusted publishing. Never publish from local npm credentials, and never create or push a release tag by hand — the workflow creates the tag, and it only does so after the build and publication have succeeded.
Which product, which version
An unqualified "release" means the next patch of Happy Agent. It never means Happy Terminal, and it never means a library.
| Request | Product | Version |
|---|---|---|
| "release" | Happy Agent | next patch |
| "release terminal" | Happy Terminal | next stable patch, never a prerelease |
| a named library | that library | next patch |
Read the current version from the published package rather than from the working tree, and confirm it against the tags:
gh release list --limit 5
git tag --list 'v0.3.*' --sort=-v:refname | head -3 # Happy Agent
git tag --list 'happy-terminal-v*' --sort=-v:refname | head -3 # Happy Terminal
npm view @slopus/happy-terminal version
If a tagged release failed before publication, its tag may exist unpublished. Advance to the next patch and dispatch again. Never reuse or move a failed tag.
Before dispatching
- Be on current
origin/main. The workflow refuses to run unlessHEADequalsorigin/mainand the ref isrefs/heads/main. Fetch and rebase first. - Reinstall after any rebase. A rebase that moves a published SDK dependency leaves
node_modulesstale, and the failure shows up as unrelated type errors:CI=true pnpm install --frozen-lockfile - Run the tests on Node 24. The repo targets Node 24; a newer Node produces failures
that are artifacts of the Node version rather than real:
The gym is a separate suite with its own failure modes. Gym failures do not necessarily block a release, but establish whether they are pre-existing before deciding — build a worktree at the commit before yours and reproduce there.export PATH="/opt/homebrew/opt/node@24/bin:$PATH" pnpm test
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.
- 4d ago First seen · 174 lines · 62 tokens per session scan A 7a0f16a7673c
release-agent is a skill published in the GitHub repository slopus/happy-agent (24 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,714 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…