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 skills add shuaiyuan17/tomo --skill lcmgit clone --depth 1 https://github.com/shuaiyuan17/tomoWrote 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/shuaiyuan17/tomo/lcm)<a href="https://agentmods.dev/skills/shuaiyuan17/tomo/lcm"><img src="https://agentmods.dev/badge/skills/shuaiyuan17/tomo/lcm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/shuaiyuan17/tomo/lcm"><img src="https://agentmods.dev/badge/skills/shuaiyuan17/tomo/lcm.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00064 | $0.01161 |
| Opus 5 | $0.00032 | $0.00580 |
| Sonnet 5 | $0.00013 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
tomo-lcm 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 12d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Management (LCM)
Manage your context window via tomo lcm CLI. Your channel key and SDK session ID are in your system prompt under # SESSION.
Mental model — hierarchical block rollups
Context is organized as a time hierarchy, each level consuming the one below:
raw tail ← today's unsummarized user/assistant events
daily block ← today's summary, covers one local-tz day
weekly block ← rolls up 7 daily blocks for one ISO week
monthly block ← rolls up weeklies for one month
yearly block ← rolls up monthlies for one year
Steady state for a long-running session: a handful of yearly blocks, ~12 monthly, 4-5 weekly, 1-7 daily, plus today raw. Total: bounded regardless of age.
Each block has a tag like daily 2026-04-17, weekly 2026-W16, monthly 2026-04, yearly 2026. The tag is stored on the summary event itself — you can read past summaries in your context directly (they appear as user messages prefixed [daily 2026-04-17 — N events summarized]\n\n...).
Daily flow
See DAILY.md — write at end of day (or mid-day when the tail gets heavy).
tomo lcm daily --session-id SESSION_ID --summary "<today's summary>"
The CLI auto-resolves today's date and finds raw events to compact. If a daily 2026-04-17 block already exists from an earlier-in-day rebuild, it's replaced (same tag, new summary absorbs newer raw events).
Weekly / Monthly / Yearly flow
See WEEKLY.md, MONTHLY.md, YEARLY.md.
tomo lcm weekly --session-id SESSION_ID --summary "<weekly summary>" # last completed ISO week
tomo lcm monthly --session-id SESSION_ID --summary "<monthly summary>" # last completed month
tomo lcm yearly --session-id SESSION_ID --summary "<yearly summary>" # last completed year
These consume block summaries already in your context — no tool calls needed to fetch source data. You just read the child blocks and synthesize.
The harness will nudge you via a <tomo-event type="lcm-rollup" ...> message when rollups are due (idempotent — catches missed Mondays etc.).
What ships with it
6 files 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.
- 12d ago First seen · 96 lines · 64 tokens per session scan A 4c52092e5cef
tomo-lcm is a skill published in the GitHub repository shuaiyuan17/tomo (5 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,161 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.