Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Tiltely/lens/plugin install lensWrote 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/tiltely/lens/setup)<a href="https://agentmods.dev/skills/tiltely/lens/setup"><img src="https://agentmods.dev/badge/skills/tiltely/lens/setup/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/tiltely/lens/setup"><img src="https://agentmods.dev/badge/skills/tiltely/lens/setup.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.00080 | $0.00777 |
| Opus 5.5 | $0.00032 | $0.00311 |
| Sonnet 5.5 | $0.00016 | $0.00155 |
| Haiku 4.5 | $0.00008 | $0.00078 |
Grade B, and why
setup scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
from other projects' sessions. Do NOT edit `~/.claude/settings.json` yourself — How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lens Setup (Claude Code)
The memory loop — a SessionEnd hook that queues lens sessions, /lens:retro to mine
them, /lens:new to grow your collection — is a Claude Code feature. Setup
creates your foundry and wires it up. Without setup, all bundled lenses and
/lens:socratic still work; setup only adds the loop.
On Claude Cowork: not supported — stop here
If you detect Cowork, do NOT set up a foundry. The memory loop does not run on Cowork:
its sandbox spawns the CLI with --setting-sources user, so plugin-provided hooks (the
SessionEnd queue) never fire, and the VM home is ephemeral. Tell the user plainly: on
Cowork, just use the lenses and /lens:socratic directly — they work fully. Run
/lens:setup on Claude Code to enable the loop there. Then stop — no foundry, no
config, no folder grant.
On Claude Code: set up the loop
The foundry holds PERSONAL session data (session IDs, project/transcript paths, mined observations) — never commit it to git. Use a private, persistent, non-tracked folder.
-
Choose the foundry location — default
~/.claude/lens-foundry/; any non-git folder is fine, but NEVER inside a git working tree. Create it with emptypending-retros.jsonlandprocessed-retros.jsonl, anobservations.mdwith a one-line header ("Cross-project learnings mined by /lens:retro; append-only"), aregistry.md(your lenses — same columns as${CLAUDE_PLUGIN_ROOT}/core/registry.md, starting empty), and an emptylenses/dir (where/lens:newwrites your global lenses;/lens:socraticreads them inline). -
Write the config at
~/.claude/lens.json(show the user first):{ "foundry": "<foundry path>" } -
Hand the user the cross-cwd permission rule so retro/hook writes never prompt from other projects' sessions. Do NOT edit
~/.claude/settings.jsonyourself — permission-widening by an agent is blocked by the auto-mode classifier by design. Print a paste-readynode -eone-liner the USER runs, merging into their settings and preserving everything else:
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.
- 1mo ago First seen · 55 lines · 80 tokens per session scan B b08eec255e11
setup is a skill published in the GitHub repository Tiltely/lens (5 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 777 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
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.