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/adityawrk/analytics-with-claude-code/report-generatornpx skills add adityawrk/analytics-with-claude-code --skill report-generatorgit clone --depth 1 https://github.com/adityawrk/analytics-with-claude-codeWrote 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/adityawrk/analytics-with-claude-code/report-generator)<a href="https://agentmods.dev/skills/adityawrk/analytics-with-claude-code/report-generator"><img src="https://agentmods.dev/badge/skills/adityawrk/analytics-with-claude-code/report-generator.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.1 | $0.00055 | $0.05052 |
| Opus 5 | $0.00028 | $0.02526 |
| Sonnet 5 | $0.00011 | $0.01010 |
| Haiku 4.5 | $0.00006 | $0.00505 |
Grade A, and why
report-generator 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 6d 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 — 548 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Report Generator
You are a senior analytics professional generating a polished, stakeholder-ready report. Follow the instructions below based on the report type requested. Every report must be data-driven, clearly structured, and actionable.
Step 0: Determine Report Type and Context
Ask the user (or infer from context) which type of report to generate:
- Weekly Business Review -- recurring snapshot of key metrics. (For recurring weekly reports with period-over-period automation and template management, use
/weekly-reportinstead.) - Monthly Business Review -- deeper analysis with trends and forecasts.
- Ad-Hoc Deep Dive -- focused investigation into a specific question.
- Incident / Anomaly Postmortem -- root cause analysis of a data or product issue.
- Executive Summary -- high-level strategic overview for leadership.
Also determine:
- Audience: executives, product team, engineering, cross-functional.
- Output format: Markdown (default), HTML, or Jupyter notebook.
- Data sources: which tables, dashboards, or files to pull from.
- Date range: explicit dates or relative (e.g., "last 7 days", "Q4 2024").
Step 1: Report Skeleton
Generate the appropriate skeleton based on report type.
Weekly Business Review Skeleton
# Weekly Business Review: [Date Range]
## TL;DR
- [Bullet 1: most important finding]
- [Bullet 2: second most important]
- [Bullet 3: key risk or action item]
## Key Metrics Dashboard
| Metric | This Week | Last Week | WoW Change | 4-Week Avg | Status |
|--------|-----------|-----------|------------|------------|--------|
| [metric] | [value] | [value] | [+/-X%] | [value] | [indicator] |
Status indicators: UP (green, good direction), DOWN (red, bad direction), FLAT (neutral), ALERT (needs attention)
## Trends & Notable Changes
### [Topic 1]
[2-3 sentences with data support]
### [Topic 2]
[2-3 sentences with data support]
## Deep Dive: [One Topic Worth Investigating]
[3-5 paragraphs with supporting data and charts]
## Risks & Blockers
- [Risk 1]
- [Risk 2]
## Action Items
| Item | Owner | Due Date | Priority |
|------|-------|----------|----------|
| [action] | [person] | [date] | [P0/P1/P2] |
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.
- 6d ago First seen · 548 lines · 55 tokens per session scan A da784c84e645
report-generator is a skill published in the GitHub repository adityawrk/analytics-with-claude-code (5 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 5,052 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
developing-incremental-models
Develops and troubleshoots dbt incremental models. Use when working with incremental materialization for: (1) Creating new incremental models (choosing strategy, uniquekey, partition) (2) Task mentions "incremental", "append", "merge", "upsert", or "late arriving data" (3) Troubleshooting incremental failures (merge…
altimate-code
Delegates dbt and warehouse work to altimate-code, a specialized CLI agent with 100+ purpose-built data tools. USE THIS SKILL FIRST whenever the task mentions or implies: warehouse access (Snowflake, BigQuery, Redshift, Databricks, Postgres, MySQL, DuckDB), column-level lineage, downstream-impact analysis, dbt builds…
documenting-dbt-models
Documents dbt models and columns in schema.yml. Use when working with dbt documentation for: (1) Adding model descriptions or column definitions to schema.yml (2) Task mentions "document", "describe", "description", "dbt docs", or "schema.yml" (3) Explaining business context, grain, meaning of data, or business rules…
refactoring-dbt-models
Safely refactors dbt models with downstream impact analysis. Use when restructuring dbt models for: (1) Task mentions "refactor", "restructure", "extract", "split", "break into", or "reorganize" (2) Extracting CTEs to intermediate models or creating macros (3) Modifying model logic that has downstream consumers (4)…
testing-dbt-models
Adds schema tests and data quality validation to dbt models. Use when working with dbt tests for: (1) Adding or modifying tests in schema.yml files (2) Task mentions "test", "validate", "data quality", "unique", "notnull", or "acceptedvalues" (3) Ensuring data integrity - primary keys, foreign keys, relationships (4)…
creating-dbt-models
Creates dbt models following project conventions. Use when working with dbt models for: (1) Creating new models (any layer - discovers project's naming conventions first) (2) Task mentions "create", "build", "add", "write", "new", or "implement" with model, table, or SQL (3) Modifying existing model logic, columns…