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/chats-is/termory/run-termorynpx skills add chats-is/termory --skill run-termorygit clone --depth 1 https://github.com/chats-is/termoryWrote 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/chats-is/termory/run-termory)<a href="https://agentmods.dev/skills/chats-is/termory/run-termory"><img src="https://agentmods.dev/badge/skills/chats-is/termory/run-termory.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.00064 | $0.02999 |
| Opus 5 | $0.00032 | $0.01499 |
| Sonnet 5 | $0.00013 | $0.00600 |
| Haiku 4.5 | $0.00006 | $0.00300 |
Grade A, and why
run-termory 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 5d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Termory is a native Tauri v2 app (WKWebView) on macOS — not Electron. Drive it
with .claude/skills/run-termory/driver.mjs, which talks to it through macOS
accessibility (osascript) and captures it with screencapture. Paths below are
relative to the repo root.
There is no CDP/DevTools handle. Tauri v2 on macOS exposes no remote-debugging
port, so Playwright's _electron, chromium-cli, and every CDP-based recipe are
dead ends here. Accessibility + screenshots is the whole surface. (xvfb is
likewise irrelevant — this is a real macOS window server, not headless Linux.)
Prerequisites
Already satisfied on this machine; no apt-get/brew step was needed. What must
be true:
- Node (v22.21.1 here) and a Rust toolchain —
npm run tauri:devbuilds both. - Accessibility permission for the terminal app running the driver
(System Settings → Privacy & Security → Accessibility). Without it every
osascriptSystem Events call fails. This was already granted here, so the first-grant prompt is unverified. - Screen Recording permission for
screencapture.
Run (agent path)
node .claude/skills/run-termory/driver.mjs launch # idempotent; prints window bounds
node .claude/skills/run-termory/driver.mjs route 2 # Cmd-1..6 rail: providers/records/favorites/search/stats/settings
node .claude/skills/run-termory/driver.mjs search "Wait agent"
node .claude/skills/run-termory/driver.mjs shot /tmp/x.png # look before selecting
node .claude/skills/run-termory/driver.mjs key down down return
node .claude/skills/run-termory/driver.mjs quit
launch spawns npm run tauri:dev detached, logs to /tmp/termory-dev.log, polls
for the process, and fails fast on a compile error instead of sitting out its
15-minute timeout. It then waits out the first session scan (settle, 8s), so
with Rust already built it returns in ~15s (measured); a cold Rust build is
minutes.
Other commands: bounds (window rect as JSON), paste <text> (IME-safe text
entry — see Gotchas), key <spec>… (cmd+k, down, return, esc, …).
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.
- 5d ago First seen · 212 lines · 64 tokens per session scan A 3440dd2b1a3b
run-termory is a skill published in the GitHub repository chats-is/termory (23 stars, last pushed 11d ago), licensed MIT. It adds 64 tokens to every session and 2,999 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…