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/update-docsnpx skills add laat/mor --skill update-docsgit 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.00035 | $0.00462 |
| Opus 5 | $0.00017 | $0.00231 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
update-docs 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
Update mor's documentation to match the current source code. Be efficient.
Steps
- Run
git log --oneline -10to see recent changes that might affect docs. - Read
src/cli.ts(commander definitions, roughly lines 60–120) for the canonical list of commands and options. - Grep
src/operations-server.tsforapp.get/app.post/app.put/app.delete/app.patchto get the canonical HTTP endpoint list. - For each doc file below, read it and only edit if there's an actual factual discrepancy with the source:
README.md— commands table, HTTP API table, examplesCLAUDE.md— database tables description, architecture overviewman/mor.1— commands, options. (Do not touch the version or date in the.THheader here — that's the release skill's job.)website/src/content/docs/cli.md— commands table, exampleswebsite/src/content/docs/getting-started.md— quick start exampleswebsite/src/content/docs/storage.md— database tableswebsite/src/content/docs/integration/mcp.md— MCP tools tablewebsite/src/content/docs/integration/http.md— REST API table
Rules
- Only fix factual inaccuracies (renamed commands, removed options, new endpoints, changed table schemas).
- Do not rewrite prose, add sections, or change tone.
- Do not edit files under
src/. - If a doc file is already correct, make no changes to it.
- If nothing needs changing across the whole sweep, say so and stop — don't manufacture work.
After editing
Show the user a summary of what changed (file + one-line per fix). Don't commit or push automatically — let the user review and run /commit themselves.
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 · 35 lines · 35 tokens per session scan A 789d6e83a75f
update-docs is a skill published in the GitHub repository laat/mor (2 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 462 once invoked, about $0.0002 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…