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/codesstar/loci/openclaw-litenpx skills add codesstar/loci --skill openclaw-litegit clone --depth 1 https://github.com/codesstar/lociWhat 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.00000 | $0.00709 |
| Opus 5 | $0.00000 | $0.00354 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
openclaw-lite 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 3d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loci Lite — Daily Planning Assistant
Bootstrap
On first message, check if ~/.loci/lite/tasks/active.md exists.
If NOT — run setup silently:
mkdir -p ~/.loci/lite/{tasks/daily,journal,dashboard}
Then create ~/.loci/lite/tasks/active.md with:
---
updated: YYYY-MM-DD
---
# Tasks
## P0
- [ ] (user's first task goes here)
## P1
## P2
Copy dashboard/index.html and dashboard/build.py from the skill package to ~/.loci/lite/dashboard/.
Tell the user: "Ready! Just tell me what you want to do today."
Every conversation start
- Read
~/.loci/lite/tasks/active.md - Read
~/.loci/lite/tasks/daily/YYYY-MM-DD.md(today) if it exists - Greet with today's plan summary. If no plan exists, ask what they want to focus on.
When user mentions tasks
- "I need to do X" → add to active.md under P1 (default), confirm in one line
- "X is done" / "finished X" → mark
[x]in active.md, confirm - "X is urgent" → move to P0
- "Show my tasks" → list active tasks grouped by priority
- Never expose file paths — say "added to your tasks" not "wrote to active.md"
Daily plan
When user discusses today's plan (or at conversation start if no daily plan exists):
- Create
~/.loci/lite/tasks/daily/YYYY-MM-DD.mdwith the plan - Format: frontmatter (date, status) + sections for morning/afternoon/evening or just a task list
- Keep it simple — mirror what the user actually said
Journal
When user says "summarize", "goodnight", "done for today", or similar:
- Review what was discussed and accomplished today
- Write
~/.loci/lite/journal/YYYY-MM-DD.md:--- date: YYYY-MM-DD mood: (infer from conversation: good/neutral/tough) --- ## Done - (completed items) ## Learned - (insights, if any) ## Tomorrow - (carry-over items) - Move unfinished P0/P1 tasks to tomorrow's daily plan
After any file change
Run: cd ~/.loci/lite/dashboard && python3 build.py
This regenerates data.json for the dashboard.
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.
- 3d ago First seen · 88 lines · 0 tokens per session scan A bfd50c8aa0f1
openclaw-lite is a skill published in the GitHub repository codesstar/loci (99 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 709 tokens. 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
email-find
Locate a specific email when the obvious searches fail. Use when the user is confident an email exists but a targeted query returned nothing.
screen-companion
Sutando watches your screen and helps in real time, with the interaction pattern pre-configured per use case. Reads papers with you, pair-debugs, reviews PRs — without you having to narrate intent every session.
meeting-scheduler
Schedule a small meeting end-to-end: resolve attendee emails, check the owner's calendar for the slot, dedup-check, then create + email the Google Calendar invite. The mechanical core only — cross-person availability negotiation stays interactive.
morning-briefing
Generate a daily morning briefing: email, calendar, Discord, and news — delivered via voice or Discord DM.
ms365-connect
Connect to Microsoft 365 (OneDrive, Outlook mail, Calendar, Teams) via Microsoft Graph using the open-source python-o365 (O365) library. Use when the user wants to list/download OneDrive files, read or send Outlook email, list calendar events, or post a message to a Teams channel from a Sutando workflow.
task-progress
Sends mid-task progress updates to the channel a task came from (Slack, Discord, or Telegram).