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.
git clone --depth 1 https://github.com/ringo380/ga-mcp-fullWrote 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/commands/ringo380/ga-mcp-full/auth-status)<a href="https://agentmods.dev/commands/ringo380/ga-mcp-full/auth-status"><img src="https://agentmods.dev/badge/commands/ringo380/ga-mcp-full/auth-status/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/commands/ringo380/ga-mcp-full/auth-status"><img src="https://agentmods.dev/badge/commands/ringo380/ga-mcp-full/auth-status.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.00016 | $0.00332 |
| Opus 5 | $0.00008 | $0.00166 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
auth-status 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 9d 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.
What it actually says
/ga-mcp-full:auth-status
Report whether ga-mcp-full can currently authenticate to Google Analytics, and which credential source it is using.
Steps
-
Run:
ga-mcp-full auth status -
Relay the output verbatim to the user. The command prints:
Authenticated: yes|noAccount: <email>— the Google Account currently logged in. May read<unknown …>for tokens issued before v0.4.0 that lack the openid/email scopes; tell the user to re-run/ga-mcp-full:auth-loginto enable account identification.Auth method: OAuth (browser flow)orApplication Default Credentials (gcloud)Credentials file:path (when OAuth cache is in use)Scopes:space-separated listToken expired: true|falseHint:present only when account identification failed; includes the remediation.
-
If
Authenticated: no, offer/ga-mcp-full:auth-loginor/ga-mcp-full:setupas next steps depending on the error message. -
If the user wants to see which account is logged in without leaving the MCP dialog, they can also invoke the
whoamiMCP tool; to switch accounts, invoke theswitch_accountMCP tool followed by/ga-mcp-full:auth-login.
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.
- 9d ago First seen · 31 lines · 16 tokens per session scan A 427260d14f93
auth-status is a command published in the GitHub repository ringo380/ga-mcp-full (0 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 332 once invoked, about $0.0001 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 commands, from other repositories
meta-attach-vault
Interactive wizard to attach an Obsidian vault to a code/dev workspace (the common case), bootstrap a standalone vault, or register a remote vault. Provisions plugins + scaffolds wiki structure + binds .env + edits .gitignore + offers a conventions picker. (Skill meta-attach-vault handles natural-language triggers.).
meta-sync-template
Propagate the reference (.template) vault's plugins, snippets, and root docs to one or more configured vaults. Interactive picker — lists each vault with online status + REST-API-plugin presence, lets you sync all or a subset, with optional --force re-clone. (Skill meta-sync-template handles natural-language triggers…
okf-export
Export a wiki subset as a shareable OKF knowledge bundle (Google's Open Knowledge Format v0.1) — slugified filenames, relative markdown links, per-folder indexes, newest-first log, conformance self-checked. (Skill wiki-export handles the flow via its okf target.).
okf-projections
Régénérer les projections OKF du wiki (index racine + index par répertoire + log) ou vérifier leur dérive (--check).
wiki-boundary
Rank the wiki's "frontier" pages — the crossroads many pages link to that stay thin inside — to decide where research would pay off. Read-only, deterministic, no LLM. The score proposes attention, not importance. (Skill wiki-boundary handles natural-language triggers.).
wiki-graph
Build a typed knowledge graph (Understand-Anything-compatible knowledge-graph.json) from a vault's wiki — articles/entities/claims/sources/topics + relationships — written to wiki-meta/graph/ + a .understand-anything/ copy for the UA dashboard. Deterministic, no LLM. (Skill wiki-graph handles natural-language…