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/hamzabellouch/agent-skills/google-analytics-admin-api-basicsnpx skills add hamzabellouch/agent-skills --skill google-analytics-admin-api-basicsgit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/google-analytics-admin-api-basics)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/google-analytics-admin-api-basics"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/google-analytics-admin-api-basics.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.00078 | $0.01653 |
| Opus 5 | $0.00039 | $0.00826 |
| Sonnet 5 | $0.00016 | $0.00331 |
| Haiku 4.5 | $0.00008 | $0.00165 |
Grade A, and why
google-analytics-admin-api-basics 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.
This is a copy
100% identical to google-analytics-admin-api-basics — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Getting Started with Google Analytics Admin API
The Google Analytics Admin API provides programmatic access to Google Analytics account and property configuration. It lets you automate account management, manage data streams, configure custom dimensions, and handle product integrations.
Enabling the API via Cloud CLI
Before making API calls, ensure the Google Analytics Admin API is enabled in your Google Cloud project.
If gcloud is not found, prompt the user to install the Google Cloud CLI before
running these commands.
-
Enable the API: Use the Cloud CLI (
gcloud) to enableanalyticsadmin.googleapis.com.gcloud services enable analyticsadmin.googleapis.com --quietWhy: Enabling the API ensures your Cloud project has the necessary quota and permissions allocated for managing Google Analytics configurations.
-
Verify API Enablement:
gcloud services list --enabled --filter="analyticsadmin.googleapis.com"
Authentication
To authenticate your API requests, you must generate Application Default Credentials (ADC) and give your account the necessary scopes. Run the following command in your terminal:
gcloud auth application-default login --scopes="https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/analytics.readonly"
Why: This configures ADC in your local environment with the required Cloud Platform and Google Analytics read-only scopes, allowing the client library to automatically authenticate your requests.
[!NOTE] Configuration Changes: Methods changing the Google Analytics account/property configuration will need the
https://www.googleapis.com/auth/analytics.editscope.
Admin API Use Cases
You can use the Google Analytics Admin API to:
- Run Data Access reports (see https://developers.google.com/analytics/devguides/config/admin/v1/access-api.md.txt for more info)
- Create Account summaries
- Manage accounts
- Provision new accounts
- Search account change history events
- Manage and create properties
- Manage property data retention settings
- Manage conversion events
- Manage custom dimensions and metrics
- Manage data streams and configure measurement protocol secrets
- Manage Firebase links
- Manage Google Ads links
- Manage key events
What ships with it
7 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.
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 · 214 lines · 78 tokens per session scan A e2fed3747a40
google-analytics-admin-api-basics is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,653 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to google-analytics-admin-api-basics, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
spec-implement
Orchestrate parallel implementation of a feature specification by dispatching coder agents batch-by-batch with code review gates between batches. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", or wants to begin coding a…
spec-create
Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture…
spec-ship
Push the current branch to GitHub and create a pull request. Use this skill when the user says "ship it", "ship this", "push to github", "create a pr", "open a pull request", "send for review", "get this reviewed", or wants to push their work and open a PR. Also use when the user says "/spec-ship" (or their host's…
spec-checkpoint
Create a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "checkpoint", "commit everything", "save my progress", "create a commit", or wants to stage and commit all current changes with a well-crafted message. Also use when the user says "/spec-checkpoint" (or…
generative-seo
Run an evidence-based SEO + GEO (Generative Engine Optimization) program for ANY website or product codebase — auditing technical SEO, writing or retrofitting content so it gets cited by ChatGPT/Perplexity/AI Overviews, tracking AI-citation visibility, refreshing competitor research, and drafting distribution posts.…
spec-verify
Verify a completed feature spec by driving the real running app — not just lint/typecheck/build — and checking off every acceptance criterion from its specs/{feature}/ folder one by one. Use this after /spec-implement finishes a spec, when the user says "test this end to end", "verify this feature actually works"…