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 wordlift/wordlift-gemini-cli-extension --skill reporting-skillgit clone --depth 1 https://github.com/wordlift/wordlift-gemini-cli-extensionWrote 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/wordlift/wordlift-gemini-cli-extension/reporting-skill)<a href="https://agentmods.dev/skills/wordlift/wordlift-gemini-cli-extension/reporting-skill"><img src="https://agentmods.dev/badge/skills/wordlift/wordlift-gemini-cli-extension/reporting-skill/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/wordlift/wordlift-gemini-cli-extension/reporting-skill"><img src="https://agentmods.dev/badge/skills/wordlift/wordlift-gemini-cli-extension/reporting-skill.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.00096 | $0.02360 |
| Opus 5 | $0.00048 | $0.01180 |
| Sonnet 5 | $0.00019 | $0.00472 |
| Haiku 4.5 | $0.00010 | $0.00236 |
Grade A, and why
reporting-skill 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 11d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Performance Report Skill
Generate comprehensive, publication-ready SEO performance reports for any website with Google Search Console and/or Google Analytics 4 access.
Overview
This skill automates the full reporting pipeline:
- Pull data from GSC and/or GA4 via authenticated API calls
- Compute metrics — before/after comparisons, daily averages, diffs
- Generate charts — time series, distributions, comparisons, heatmaps
- Run statistical analysis — optional CausalImpact for A/B testing
- Produce a PDF report — structured, branded, with embedded charts
Prerequisites
Before running this skill, ensure the user has:
- A Google Cloud project with the following APIs enabled:
- Google Search Console API (for GSC data)
- Google Analytics Data API v1 (for GA4 data)
- An OAuth 2.0 Client ID (Desktop app type) → downloaded as
client_secret.json - The GA4 Property ID (numeric, found in GA4 Admin → Property Settings)
- The GSC property URL (e.g.,
https://www.example.com/)
Step-by-Step Instructions
Step 1: Gather Configuration
Ask the user for the following information. Create a config.yaml file in the project's working directory using the template:
| Parameter | Required | Example |
|---|---|---|
site.domain |
Yes | https://www.example.com |
site.name |
Yes | Example Corp |
gsc.enabled |
Yes | true or false |
gsc.client_secret |
If GSC | Path to client_secret.json |
gsc.credentials_cache |
If GSC | Path to credentials.json (auto-created) |
ga4.enabled |
Yes | true or false |
ga4.property_id |
If GA4 | 396994319 |
ga4.client_secret |
If GA4 | Path to client_secret.json |
ga4.credentials_cache |
If GA4 | Path to ga4_credentials.json (auto-created) |
dates.before_start |
Yes | 2026-01-01 |
dates.before_end |
Yes | 2026-01-31 |
dates.after_start |
Yes | 2026-02-01 |
dates.after_end |
Yes | 2026-02-28 |
groups.variant_csv |
No | Path to CSV with url column |
groups.control_csv |
No | Path to CSV with url column |
output.directory |
Yes | ./output |
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/config_template.yaml 3.4 KB
- assets/report_template.md 7.4 KB
- README.md 3.0 KB
- references/CONFIG.md 3.2 KB
- references/METRICS.md 3.0 KB
- scripts/analyze.py 34 KB runs code
- scripts/compute_roas.py 18 KB runs code
- scripts/ga4_pull.py 12 KB runs code
- scripts/google_ads_analysis.py 4.9 KB runs code
- scripts/gsc_pull.py 11 KB runs code
- scripts/report.py 21 KB runs code
- scripts/setup.py 981 B runs code
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.
- 11d ago First seen · 253 lines · 96 tokens per session scan A 086a104e0041
reporting-skill is a skill published in the GitHub repository wordlift/wordlift-gemini-cli-extension (2 stars, last pushed 4mo ago), licensed MIT. It adds 96 tokens to every session and 2,360 once invoked, about $0.0005 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
compound-docs
Document solved problems for knowledge persistence.
mobile
React Native, Flutter, and mobile development best practices.
tailwind
Tailwind CSS v4 patterns, design systems, and responsive design.
api-design
RESTful API patterns, GraphQL design, and API best practices.
nextjs
Next.js App Router architecture, Server Components, and modern patterns.
performance
Performance profiling, optimization techniques, and caching strategies.