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/observability)<a href="https://agentmods.dev/skills/tiltely/lens/observability"><img src="https://agentmods.dev/badge/skills/tiltely/lens/observability/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/observability"><img src="https://agentmods.dev/badge/skills/tiltely/lens/observability.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.01474 |
| Opus 5.5 | $0.00032 | $0.00590 |
| Sonnet 5.5 | $0.00016 | $0.00295 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
observability 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 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.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Lens of Observability
Read first: ${CLAUDE_PLUGIN_ROOT}/core/protocol.md and ${CLAUDE_PLUGIN_ROOT}/core/dossier.md. Dossier rules: read it, skip answered questions WITH skip lines, append your outputs.
This lens examines the OPERATIONAL angle the other lenses miss: not "is the happy path correct" (that's design/tdd) but "when it silently breaks at 3am, how do we KNOW, and how does the stuck user/record get recovered". Its obsession is the orphan — a user or record stranded mid-flow because an external event was lost or a step failed with nothing watching.
Mode selection
- Explicit argument wins ("audit" / "design").
- Otherwise infer: planning new work → design; reviewing existing code → audit. Confirm your inference in one line before starting.
Before asking anything
- Read the dossier if valid — resolve it per dossier.md (the branch-scoped path). Skip answered questions WITH skip lines.
- Note which surfaces exist (payments, webhooks, multi-step flow, background jobs) — they select Tier 2.
Question battery — design mode
Ask one at a time; follow answers per protocol.md. Append answers to the dossier.
Tier 1 — framing (always)
- Name the worst SILENT failure here: a user or record stuck mid-flow that NOTHING surfaces (paid-but-no-access, charged-twice, half-migrated, webhook-lost, stuck-PROCESSING). If you cannot name one, say so — maybe this flow does not need the lens.
- When that breaks at 3am, how do you find out, and from what? An alert, a user complaint, a dashboard, or nothing until someone notices? Who is on the hook?
Tier 2 — surface-conditional
If external events / webhooks (Stripe, SendGrid, queues, partner callbacks): 3. What happens when an inbound event is LOST, or arrives LATE / out-of-order? Is there a reconciliation job that re-derives truth from the SOURCE (the provider's API), or is the event the only signal you trust? 4. Is event processing idempotent and deduped DURABLY (a table, not an in-memory Set)? Can a redelivery double-apply an effect (double charge, double grant)?
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 · 120 lines · 80 tokens per session scan A b7d5d246ccbe
observability 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 1,474 once invoked, about $0.0003 per session on Opus 5.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, 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…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.