Lotti is a private logbook that stores tasks, time records, notes, habits, and health data on a person's devices, with personal AI assistants that summarize records and suggest changes for approval. It is for people who want to track intended and completed work while keeping synchronized data end-to-end encrypted. The catalogue add-ons provide agents, skills, and instructions for working with Lotti.
Borrowing it
Nothing to install: this file belongs to matthiasn/lotti. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/matthiasn/lotti/main/.claude/skills/analyze-db-logs/SKILL.mdgit clone --depth 1 https://github.com/matthiasn/lottiWrote 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/matthiasn/lotti/analyze-db-logs)<a href="https://agentmods.dev/skills/matthiasn/lotti/analyze-db-logs"><img src="https://agentmods.dev/badge/skills/matthiasn/lotti/analyze-db-logs/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/matthiasn/lotti/analyze-db-logs"><img src="https://agentmods.dev/badge/skills/matthiasn/lotti/analyze-db-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.03696 |
| Opus 5 | $0.00023 | $0.01848 |
| Sonnet 5 | $0.00009 | $0.00739 |
| Haiku 4.5 | $0.00005 | $0.00370 |
Grade A, and why
analyze-db-logs 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 10d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 10d ago First seen · 331 lines · 46 tokens per session scan A 8eb3311cb7ff
analyze-db-logs is a skill published in the GitHub repository matthiasn/lotti (1,171 stars, last pushed today), licensed GPL-3.0. It adds 46 tokens to every session and 3,696 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-30.
Other skills, from other repositories
boutique-store
Create and use Boutique Store for Swift data persistence, including initialization, @Stored controllers, CRUD operations, operation chaining, and granular event monitoring. Use when persisting arrays of items, building data controllers, or working with Boutique's Store type.
boutique-stored-values
Persist individual values with Boutique's @StoredValue (UserDefaults) and @SecurelyStoredValue (Keychain), including set, reset, toggle, bindings, keypath setters, array and dictionary helpers, and async observation. Use when storing preferences, settings, feature flags, or sensitive data like auth tokens.
qdrant-monitoring-debugging
Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.
performance
Use when optimizing application performance — caching strategies, eager loading, query optimization, Redis patterns, or background job design.
perf-engineering
A guide to finding and fixing slow code, excessive memory use, slow startup, repeated database queries, and inefficient caching.
stale-derived-state
Diagnose a change that does not take effect until a reload, a logout or a navigation away and back, because a cache or a piece of derived state has no invalidation hook on write. Use when a save appears to work but the screen keeps showing the old value. Names the Crumbtrail queries that prove the write landed, and…