lens-report

lens-report is a skill for Claude Code from tonone-ai/tonone. It costs 51 tokens per session (1,260 once invoked), scanned A, original, MIT.

A reporting pipeline that runs SQL queries on a schedule and sends reports through email or Slack, with threshold alerts and comparisons with earlier results.

In plain words
What is it for?
Use it to build scheduled digests, choose data sources and delivery channels, write metric queries, and compare results over time.
Why use it?
It removes repeated manual report preparation and can draw attention to metrics when they cross a chosen threshold.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool; mentions Claude Code.

Part of the engineering-team plugin — 80 skills shipped together

Good fit Use it to build scheduled digests, choose data sources and delivery channels, write metric queries, and compare results over time.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tonone-ai/tonone/lens-report
Install

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.

Any agent
npx skills add tonone-ai/tonone --skill lens-report
Clone the repo
git clone --depth 1 https://github.com/tonone-ai/tonone

Made for: Claude Code.

Or install engineering-team, the plugin that ships this one along with the rest of its 80 skills.

Wrote 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.

agentmods badge for lens-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/tonone-ai/tonone/lens-report/github.svg)](https://agentmods.dev/skills/tonone-ai/tonone/lens-report)
Your own site
<a href="https://agentmods.dev/skills/tonone-ai/tonone/lens-report"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/lens-report/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.

agentmods 80×15 button for lens-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/tonone-ai/tonone/lens-report"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/lens-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,260 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.01260
Opus 5.5 $0.00020 $0.00504
Sonnet 5.5 $0.00010 $0.00252
Haiku 4.5 $0.00005 $0.00126

Measured 17d ago against content hash e11a53303b2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lens-report 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.

bundle/engineering-team/skills/lens-report/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build Reporting Pipeline

You are Lens — the data analytics and BI engineer from the Engineering Team.

Steps

Step 0: Detect Environment

Scan workspace for data and scheduling infrastructure:

  • Database configs — connection strings, ORM configs (what data source)
  • docker-compose.yml — check for Airflow, Prefect, Dagster, or cron-based scheduling
  • .github/workflows/ — GitHub Actions (can schedule reports)
  • crontab, systemd timers — simple scheduling
  • Slack webhook URLs or bot tokens in config/env
  • Email/SMTP configuration
  • Existing report scripts or SQL queries
  • dbt_project.yml — dbt for transformation before reporting

Identify: data source, scheduling mechanism, delivery channel.

Step 1: Understand the Report Requirements

Determine (from context or by asking):

  • What metrics? — which numbers matter for this report
  • Who receives it? — stakeholders, team, leadership
  • What frequency? — daily, weekly, monthly (weekly is usually the sweet spot)
  • What triggers action? — what should make someone stop and investigate
  • What format? — Slack message, email, PDF, dashboard link

Step 2: Build SQL Queries

For each metric in the report, create SQL returning:

  • Current value — metric for this reporting period
  • Previous period — same metric for last period (week-over-week, month-over-month)
  • Change — absolute and percentage change
  • Threshold status — above/below target
-- Example: Weekly active users with comparison
WITH current_week AS (
    SELECT COUNT(DISTINCT user_id) AS active_users
    FROM events
    WHERE event_date >= current_date - interval '7 days'
),
previous_week AS (
    SELECT COUNT(DISTINCT user_id) AS active_users
    FROM events
    WHERE event_date >= current_date - interval '14 days'
      AND event_date < current_date - interval '7 days'
)
SELECT
    c.active_users AS current,
    p.active_users AS previous,
    c.active_users - p.active_users AS change,
    ROUND((c.active_users - p.active_users)::numeric / NULLIF(p.active_users, 0) * 100, 1) AS pct_change
FROM current_week c, previous_week p;

Read the full file on GitHub · 159 lines

Changes

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.

  1. 17d ago First seen · 159 lines · 51 tokens per session scan A e11a53303b2f

Subscribe to this mod's changes

lens-report is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 1,260 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.

Related

Other skills, from other repositories

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…

lukasrepublic/agentic-foundry · 291 tokens

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…

lukasrepublic/agentic-foundry · 133 tokens

bullmq-jobs

Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.

lukasrepublic/agentic-foundry · 0 tokens

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…

lukasrepublic/agentic-foundry · 185 tokens

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…

lukasrepublic/agentic-foundry · 141 tokens

triage-report

Drain the .review/ report queue. Resolves un-triaged scan/audit reports (producer-agnostic — check-docs-consistency and any other scanner), dispatches the triage-report subagent (Sonnet) one report at a time for per-finding dispositions (promote / patch / dup / needs-investigation / dismiss), then the gateway absorbs…

RockyHong/super-bootstrap · 151 tokens