Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DorianSchlede/nexus-templatenpx agentmods add skills/dorianschlede/nexus-template/google-connectWrote 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/dorianschlede/nexus-template/google-connect)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/google-connect"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/google-connect.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.00012 | $0.02108 |
| Opus 5 | $0.00006 | $0.01054 |
| Sonnet 5 | $0.00002 | $0.00422 |
| Haiku 4.5 | $0.00001 | $0.00211 |
Grade A, and why
google-connect 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 8d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Connect
Setup wizard for Google Workspace integration.
Purpose
Guide users through connecting their Google account to Nexus. One OAuth setup grants access to all 7 Google services: Gmail, Docs, Sheets, Calendar, Drive, Tasks, and Slides.
Shared Resources
This skill uses google-master shared library:
| Resource | When to Load |
|---|---|
google-master/scripts/check_google_config.py |
Always first (pre-flight) |
google-master/scripts/google_auth.py |
For authentication |
google-master/references/setup-guide.md |
Detailed setup instructions |
google-master/references/error-handling.md |
On any errors |
Workflow 0: Config Check (ALWAYS FIRST)
Every interaction MUST start with config validation:
uv run python 00-system/skills/google/google-master/scripts/check_google_config.py --json
Exit code meanings:
- Exit 0: Fully configured and authenticated - ready to use
- Exit 1: Credentials exist but need to login (run OAuth flow)
- Exit 2: Missing credentials - need full setup
Route based on exit code:
- Exit 0 → Workflow 4 (Already Connected)
- Exit 1 → Workflow 3 (Authenticate)
- Exit 2 → Workflow 1 (Full Setup)
Workflow 1: Full Setup (First-Time Users)
Triggers: "connect google", "setup google", config check returns exit 2
Purpose: Guide user through complete Google Cloud setup.
Step 1: Introduction
Display:
--- GOOGLE WORKSPACE SETUP ---------------------------------
This will connect Nexus to your Google account, enabling:
📧 Gmail - Read, send, manage emails
📄 Docs - Create and edit documents
[STATS] Sheets - Work with spreadsheets
[DATE] Calendar - Manage events and schedules
[DIR] Drive - Upload, download, organize files
[OK] Tasks - Create and manage task lists
📽️ Slides - Create and edit presentations
Time: ~10 minutes (one-time setup)
You'll need: A Google account and browser access
------------------------------------------------------------
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.
- 8d ago First seen · 376 lines · 12 tokens per session scan A 27a4b1c49754
google-connect is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 2,108 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…