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/tiltely/lens/retronpx skills add Tiltely/lens --skill retrogit clone --depth 1 https://github.com/Tiltely/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/retro)<a href="https://agentmods.dev/skills/tiltely/lens/retro"><img src="https://agentmods.dev/badge/skills/tiltely/lens/retro.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.00060 | $0.00757 |
| Opus 5 | $0.00030 | $0.00378 |
| Sonnet 5 | $0.00012 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
retro 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lens Retro
Requires a lens config with foundry set (a Claude Code feature — the loop is not
supported on Cowork; see /lens:setup). Discover the config first-readable-wins:
$LENS_CONFIG → ~/.claude/lens.json → ~/lens/lens.json. If none is found: explain
in one line, point to /lens:setup, stop. Never error.
Compute the pending set
- Read
<foundry>/pending-retros.jsonland<foundry>/processed-retros.jsonl. - Pending = entries whose
session_idis NOT in the processed file. (Both files are append-only. NEVER rewrite or truncate them — a SessionEnd hook may append concurrently.) - Gap entries (
"type":"gap") are pending until a processed marker with their date+lens+note hash appears; treat each as a one-line observation candidate. - If the user passed an explicit transcript/session argument, process only that.
Process each entry (serially, v1)
For session entries, read the transcript (it is JSONL; grep/skim for the lens questions, user answers, friction moments — do not load the whole file blindly if it is huge). Ask of each:
- What questions arose that NO current lens covers? (check core/registry.md)
- Did a lens perform poorly — wrong tier order, dumb question, missed follow-up?
- Did durable PROJECT facts surface that are missing from that project's CLAUDE.md? If the transcript file no longer exists: mark processed, note "transcript gone", skip.
Cross-entry synthesis
After individual passes, look across entries for repetition. A pattern seen ≥2 times is a proposal candidate:
- New lens → name it, one-line purpose, 3 sample questions → on approval, hand to
/lens:new (which writes it to your global foundry, a project
.lens/, or — for maintainers — the bundled set). - Lens update → for a lens you created (in
<foundry>/lenses/or a project.lens/): concrete diff, apply on approval. For a bundled lens: if the session is inside the lens plugin repo (maintainer context), apply the diff there; otherwise emit it as a local file and suggest a PR to the public plugin repo. - CLAUDE.md update → concrete diff, addressed to the specific project's CLAUDE.md.
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 · 60 lines · 60 tokens per session scan A 2c7c56cf320d
retro is a skill published in the GitHub repository Tiltely/lens (5 stars, last pushed 25d ago), licensed MIT. It adds 60 tokens to every session and 757 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
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…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…