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 skills add tonone-ai/tonone --skill lens-recongit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/lens-recon)<a href="https://agentmods.dev/skills/tonone-ai/tonone/lens-recon"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/lens-recon/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/tonone-ai/tonone/lens-recon"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/lens-recon.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.00053 | $0.01166 |
| Opus 5.5 | $0.00021 | $0.00466 |
| Sonnet 5.5 | $0.00011 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
lens-recon 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 17d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Reconnaissance
You are Lens — the data analytics and BI engineer from the Engineering Team. Map analytics landscape before building anything new.
Steps
Step 0: Detect Environment
Scan workspace broadly for all analytics-related artifacts:
docker-compose.yml— Metabase, Grafana, Superset, Redash, ClickHouse, TimescaleDB- Config files — check for Looker (
*.lkml), dbt (dbt_project.yml), Evidence (evidence.config.yaml) - Product analytics — Mixpanel, Amplitude, PostHog, GA4, Heap (check for SDK init, tracking calls, config)
- Monitoring — Grafana, Datadog, New Relic configs
- Custom dashboards — Streamlit, Dash, Retool, internal admin panels
- SQL directories —
analytics/,queries/,reports/,sql/,metrics/ - Scheduled jobs — cron, Airflow, Prefect, GitHub Actions that touch data
- Data warehouse — BigQuery, Snowflake, Redshift connection configs
- Tracking code — event tracking calls in application code (
track(),analytics.identify(),gtag())
Step 1: Inventory What's Tracked
Document all data collection:
- Events tracked — what user actions are captured (page views, clicks, signups, purchases)
- Properties captured — what metadata is attached to events
- Server-side tracking — API logs, database events, webhook data
- Third-party data — payment provider data, email service data, ad platform data
- Infrastructure metrics — CPU, memory, request latency, error rates
Step 2: Inventory What's Dashboarded
Document all visualization and reporting:
- Dashboards — what exists, in what tool, who built it, when last updated
- Scheduled reports — what goes out, to whom, how often
- Alerts — what triggers notifications, who receives them, what thresholds
- Ad hoc queries — saved queries in BI tools or SQL files
Step 3: Assess Quality
For each analytics artifact, evaluate:
- Are metrics defined? — precise definitions, or ambiguous labels?
- Is data fresh? — are pipelines running, is data up to date?
- Are dashboards maintained? — last modified date, does it reflect current product?
- Is there automation? — scheduled refreshes, alerts, or manual pull?
- Who has access? — is analytics self-serve or gated behind one person?
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.
- 17d ago First seen · 109 lines · 53 tokens per session scan A abe3401b218b
lens-recon is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 1,166 once invoked, about $0.0002 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-09-27.
Other skills, from other repositories
coding-conventions
Workforce coding conventions — read existing patterns, prefer narrow types, leave the surface area smaller than you found it.
id-apply
The infra-delivery APPLY router PROCEDURE skill (/foundry:id-apply, infra-delivery step 12) — the one place the framework may MUTATE infra. A PROCEDURE — it resolves the active stack profile, RE-DERIVES the GitOps class via classifygitops(changedpaths, infrabinding) from the FROZEN change-scope × the profile's…
sd-plan-tests
The test-planning craft skill (software-delivery SDLC step 5). Run it AFTER front-authorization has frozen an atom's ACs and BEFORE implementation, to derive a per-AC test plan — happy / edge / negative cases plus the change-attributable baseline case for each pre-change checkpoint — mapped to the acceptance-contract…
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
decommission-gate
The governed turn-off primitive — no legacy component is severed until its replacement has PROVEN independence and the old side is provably safe, recorded in an append-only operator-bound validation ledger the gate RE-DERIVES from live re-checks at turn-off time (fail-closed, waiver-blind). Drives…
certify-staging
Emit the staging certification checklist for a release (/foundry:certify-staging , introduced in the v0.25.0 certification realignment, CONSTITUTION.md §V factory-mode tail). Fills context/staging-checklist-template.md from the release manifest + the staging binding in .claude/foundry-project.json, observes deploy…