AuC is a Python framework for running a single AI agent with an asynchronous, pluggable reasoning loop, language-model adapters, permission levels, and observable events. It is used to build coding and conversational agents with tools, security checks, web interfaces, background jobs, evaluations, and isolated execution. The catalogue entries are skills for extending its agent workflow.
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 ufy2024/AuC --skill google-workspace-opsgit clone --depth 1 https://github.com/ufy2024/AuCWrote 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/ufy2024/auc/google-workspace-ops)<a href="https://agentmods.dev/skills/ufy2024/auc/google-workspace-ops"><img src="https://agentmods.dev/badge/skills/ufy2024/auc/google-workspace-ops/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/ufy2024/auc/google-workspace-ops"><img src="https://agentmods.dev/badge/skills/ufy2024/auc/google-workspace-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 22 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00059 | $0.00686 |
| Opus 5.5 | $0.00024 | $0.00274 |
| Sonnet 5.5 | $0.00012 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
google-workspace-ops 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 1mo 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
92% identical to google-workspace-ops — 26 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Workspace Ops
This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.
When to Use
- User needs to find a doc, sheet, or deck and update it in place
- Consolidating plans, trackers, notes, or customer lists stored in Google Drive
- Cleaning or restructuring a shared spreadsheet
- Importing, repairing, or reformatting a Google Slides deck
- Producing summaries from Docs, Sheets, or Slides for decision-making
Preferred Tool Surface
Use Google Drive as the entry point, then switch to the right specialist:
- Google Docs for text-heavy docs
- Google Sheets for tabular work, formulas, and charts
- Google Slides for decks, imports, template migration, and cleanup
Do not guess structure from filenames alone. Inspect first.
Workflow
1. Find the asset
Start with the Drive search surface to locate:
- the exact file
- sibling assets
- likely duplicates
- recently modified versions
If several documents look similar, confirm by title, owner, modified time, or folder.
2. Inspect before editing
Before making changes:
- summarize current structure
- identify tabs, headings, or slide count
- detect whether the task is local cleanup or structural surgery
Pick the smallest tool that can safely perform the work.
3. Edit with precision
- For Docs: use index-aware edits, not vague rewrites
- For Sheets: operate on explicit tabs and ranges
- For Slides: distinguish content edits from visual cleanup or template migration
If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.
4. Keep the working system clean
When the file is part of a larger workflow, also surface:
- duplicate trackers
- outdated decks
- stale docs vs canonical docs
- whether the asset should be archived, merged, or renamed
Output Format
Use:
ASSET
- file name
- type
- why this is the right file
CURRENT STATE
- structure summary
- key problems or blockers
ACTION
- edits made or recommended
FOLLOW-UPS
- archive / merge / duplicate cleanup / next file to update
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.
- 1mo ago First seen · 116 lines · 59 tokens per session scan A 2e522b6e5552
google-workspace-ops is a skill published in the GitHub repository ufy2024/AuC (1,080 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 686 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to google-workspace-ops, differing in 26 lines, and is treated as a copy.
Other skills, from other repositories
google-workspace-ops
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
slack-report-delivery
Deliver formatted network reports, audit results, topology diagrams, and compliance documentation to Slack channels with rich Block Kit formatting. Use when posting a health check report, sharing a security audit, delivering topology diagrams, or sending scheduled network reports to Slack.
资料库
A workflow for managing WorkBuddy's shared content area, including online documents, structured tables, pages, links, and stored files. It supports content creation, organisation, sharing, collaboration, and light publishing.
aaif-sync-chapters
Push accepted intake cities and organizer names onto the public Chapters List sheet — appending a row for a city that has none, merging organizer names into the row that exists — and audit every chapter row's Luma page. Reports and proposes by default; writes only on explicit approval. Use when asked to add a new city…
estimate
A development-estimation tool that analyzes project plans or source code and creates an Excel estimate grouped by development, labor, cloud, API, and miscellaneous costs.
update-status
This skill should be used when the user wants to change the status of a job already in the tracker (List.xlsx), especially after a company responds. Triggers on phrases like "[company] called me back", "[company] replied", "got an interview with [company]", "move [company] to in progress", "set [company] to in…