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 IAPro-Community/Orquestrador-Maestro --skill skill-google-workspace-syncgit clone --depth 1 https://github.com/IAPro-Community/Orquestrador-MaestroWrote 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/iapro-community/orquestrador-maestro/skill-google-workspace-sync)<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-google-workspace-sync"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-google-workspace-sync/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/iapro-community/orquestrador-maestro/skill-google-workspace-sync"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-google-workspace-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 19 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 35 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00057 | $0.00828 |
| Opus 5 | $0.00028 | $0.00414 |
| Sonnet 5 | $0.00011 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
skill-google-workspace-sync 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 12d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Workspace Sync
Use this skill when a product connects Google accounts, syncs calendars or files, creates events, generates Meet links, calculates availability, or reconciles Workspace data.
Core Workflow
- Confirm the exact product surface and minimum scopes: Calendar, Events, FreeBusy, Meet, Drive, Sheets, or a combination.
- Use server-side OAuth with
GOOGLE_CLIENT_ID,GOOGLE_CLIENT_SECRET, and encrypted refresh tokens. - Request only the scopes needed for the current workflow. Store granted scopes and block features that require scopes the user did not grant.
- Before each API call, use one token function that refreshes expired access tokens, persists token state, and handles revocation.
- Normalize external resources with provider account ID, local owner, external ID, calendar or file ID,
etag,updated_at, timezone, and sync status. - Use idempotency for writes. For Meet links, send a stable
requestIdand store the returned conference data. - Treat webhooks as hints, not complete truth. Run reconciliation jobs to catch missed notifications, remote deletes, conflicts, and token failures.
- Queue bulk sync and retryable writes. Keep user-facing requests short and return job status for long operations.
- Validate dates, timezones, attendees, file permissions, sheet ranges, and ownership before writing remote or local state.
- Keep audit events for connect, scope change, create, update, delete, sync conflict, token refresh failure, and disconnect.
API Maintenance Boundary
- Treat Calendar, Drive, Sheets, and Meet as separate APIs with separate enablement and scope review; do not grant a broad Workspace scope because one feature needs only one resource.
- Use the official Google client libraries or REST discovery documents and pin dependency versions through the host project's normal lockfile process.
- Re-check OAuth consent, verification, incremental authorization, push notification channels, and resource-specific quotas when adding a new Workspace surface.
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.
- 12d ago First seen · 74 lines · 57 tokens per session scan A d80e38e83856
skill-google-workspace-sync is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (42 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 828 once invoked, about $0.0003 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-30.
Other skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
webhook-subscriptions
Webhook subscriptions: event-driven agent runs.
composio
Build AI agents and apps with Composio - access 200+ external tools with Tool Router or direct execution.
zapier-sdk
Zapier SDK for TypeScript. Programmatic access to 9,000+ apps on a user's behalf via Zapier's OAuth and audit layer. Use when writing code that needs to run actions in third-party apps (send an email, upsert a CRM record, look up a spreadsheet row, post to a chat) without managing per-app OAuth or vendor SDKs.…
fortify
Use when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.
annie-universal-api-orchestrator
Use AGNT's stored OAuth tokens and API keys for a third-party API only when no suitable authenticated AGNT tool exists or a working tool lacks the required API capability. Existing provider tools are always the first choice.