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 orieg/gws-connector --skill reauthgit clone --depth 1 https://github.com/orieg/gws-connectorWrote 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/orieg/gws-connector/reauth)<a href="https://agentmods.dev/skills/orieg/gws-connector/reauth"><img src="https://agentmods.dev/badge/skills/orieg/gws-connector/reauth.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.00025 | $0.00661 |
| Opus 5 | $0.00013 | $0.00331 |
| Sonnet 5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
reauth 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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Re-authorize Account
Re-run OAuth for an existing account. This refreshes the token and picks up any new scopes added in the GCP project — without changing the account label, default status, or credentials.
When to use
- After adding new OAuth scopes in the GCP Console (e.g., adding
gmail.send) - When token refresh fails with auth errors
- When the user gets permission denied on a specific API
- When upgrading from v0.2.x to v0.3.0+ (Sheets and Docs scopes are new)
- When picking up the Google Slides tools (the
presentationsscope is new)
Upgrading to v0.3.0 — tell the user before re-auth
If the user is re-authorizing because they just upgraded to v0.3.0 (or later),
they must approve two new scopes. Before calling gws.accounts.reauth, say
this to them (adapt to their wording):
The v0.3.0 release adds Google Sheets and Google Docs support. Re-authorizing grants this server read and write access to every spreadsheet and document in this account's Google Drive, including files shared with the account. Make sure this matches your intent before approving the browser consent screen. You also need to have added the
spreadsheetsanddocumentsscopes (and enabled the Sheets and Docs APIs) in the GCP project's OAuth consent screen — otherwise consent will fail.
Do not proceed with gws.accounts.reauth until the user has acknowledged this.
Picking up the Google Slides tools — tell the user before re-auth
If the user is re-authorizing to enable the Google Slides tools
(gws.slides.*), they must approve one new scope. Before calling
gws.accounts.reauth, say this to them (adapt to their wording):
The Slides tools add the
presentationsscope, granting this server read and write access to every Google Slides presentation in this account's Drive, including files shared with the account. You also need to have enabled the Slides API and added thepresentationsscope in the GCP project's OAuth consent screen — otherwise consent will fail.
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.
- 7d ago First seen · 57 lines · 25 tokens per session scan A 28c1c41f1ea3
reauth is a skill published in the GitHub repository orieg/gws-connector (1 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 661 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 skills, from other repositories
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
google-ads-landing
Score and diagnose Google Ads landing pages. Use when asked to audit a landing page, check landing page quality, diagnose high-CTR but low-conversion-rate ad groups, improve Quality Score's Landing Page Experience component, or compare an ad group's messaging against its landing page. Trigger on "landing page audit"…
content-planner
GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks…
keyword-research
Discover, analyze, and prioritize keywords for SEO and GEO content strategies from a seed keyword or niche. Identifies high-value opportunities based on search volume, competition, intent, and business relevance. Generates topic clusters. For building a dated editorial calendar from your own Search Console data, use…
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
schema-markup-generator
Generate JSON-LD structured data markup for rich results in Google Search. Supports FAQ, HowTo, Article, Product, LocalBusiness, and multi-type schemas. Validates against Google requirements and provides implementation guidance. Use when asked to "add schema markup", "generate structured data", "JSON-LD", "rich…