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/laat/mor/releasenpx skills add laat/mor --skill releasegit clone --depth 1 https://github.com/laat/morWhat 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.00019 | $0.00501 |
| Opus 5 | $0.00010 | $0.00251 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
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 yesterday.
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
Create a release for mor. The user provides the version number (e.g. /release v0.12.0).
Steps
-
Parse version: Strip leading
vif present to get the semver (e.g.0.12.0). The tag usesvprefix (e.g.v0.12.0). -
Pre-flight check: Run
pnpm prepublishOnly(lint, test, build) before making any changes. If it fails, stop and fix the issues first. -
Find previous release tag: Run
gh release list --limit 1to get the latest release tag. -
Build changelog: Run
git log <previous-tag>..HEAD --onelineto get all commits since the last release. Group them into sections:- Features — new functionality
- Fixes — bug fixes
- Docs — documentation changes
- Internal — refactoring, tests, build changes
Skip version bump commits. Write concise user-facing descriptions, not raw commit messages.
-
Show the changelog to the user and ask for approval before proceeding.
-
Bump version: Update
versioninpackage.json,.claude-plugin/plugin.json, and the.THheader line ofman/mor.1to the new semver. The.THline inman/mor.1also carries a release date — update it to today's date inYYYY-MM-DDformat. Format:.TH MOR 1 "<date>" "mor <semver>" "User Commands". -
Commit and push: Commit with message
<semver>(e.g.0.12.0), then push. -
Create GitHub release: Run
gh release create v<semver>with the changelog as the body. Use## What's newas the top-level heading. -
Publish to npm: Publishing happens automatically via the
publish.ymlGitHub Actions workflow, triggered by thev*tag created in step 8. No manual publish step is needed.
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.
- yesterday First seen · 34 lines · 19 tokens per session scan A d27794b4916f
release is a skill published in the GitHub repository laat/mor (2 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 501 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…