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 aAAaqwq/AGI-Super-Team --skill client-workspacegit clone --depth 1 https://github.com/aAAaqwq/AGI-Super-TeamWrote 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/aaaaqwq/agi-super-team/client-workspace)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/client-workspace"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/client-workspace.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.01028 |
| Opus 5 | $0.00009 | $0.00514 |
| Sonnet 5 | $0.00004 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
client-workspace 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 3d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Workspace
Create and manage client folders in Google Drive — shared docs, questionnaires, proposals, pre-call checks.
When to use
- "create workspace for [client]"
- "set up folder for [client]"
- "share doc with [client]"
- "check docs before call with [client]"
- Before any consulting call — verify shared docs are accessible
- After creating a questionnaire, proposal, or contract for a client
Dependencies
- Other skills:
google-drive,query-leads(CRM lookup) - External: Python 3, google-api-python-client
Paths
| What | Path |
|---|---|
| Drive Manager | $GOOGLE_TOOLS_PATH/drive_manager.py |
| Token | $GOOGLE_TOOLS_PATH/token.json |
| Venv Python | $GOOGLE_TOOLS_PATH/.venv/bin/python3 |
| CRM People | $DATA_PATH/sales/crm/contacts/people.csv |
| CRM Companies | $DATA_PATH/sales/crm/contacts/companies.csv |
Known Folder IDs
| Folder | ID |
|---|---|
| Clients (root) | <YOUR_CLIENTS_FOLDER_ID> |
Standard Folder Structure
Clients/
{CompanyName}/
Discovery/ -- questionnaires, call notes, research
Proposals/ -- scoping docs, estimates, quotes
Contracts/ -- signed agreements, NDAs
Deliverables/ -- work product, reports
How to execute
Step 1: Create client workspace
DM="$GOOGLE_TOOLS_PATH/.venv/bin/python3 $GOOGLE_TOOLS_PATH/drive_manager.py"
CLIENTS_ROOT="<YOUR_CLIENTS_FOLDER_ID>"
# Create company folder
$DM create-folder "CompanyName" --parent $CLIENTS_ROOT
# Note the folder ID from output, then create subfolders:
$DM create-folder "Discovery" --parent COMPANY_FOLDER_ID
$DM create-folder "Proposals" --parent COMPANY_FOLDER_ID
$DM create-folder "Contracts" --parent COMPANY_FOLDER_ID
$DM create-folder "Deliverables" --parent COMPANY_FOLDER_ID
Step 2: Create shared doc (questionnaire, proposal, etc.)
Write HTML content to a temp file, then create Google Doc:
# Create doc from HTML
$DM create-doc "Client J — Pre-call Questionnaire" --folder DISCOVERY_FOLDER_ID --html /tmp/questionnaire.html
# Share with client
$DM share DOC_ID --email [email protected] --role writer --notify --message "Please fill in before our call"
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.
- 3d ago First seen · 140 lines · 18 tokens per session scan A 1f70e3938704
client-workspace is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (91 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,028 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-09-05.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
upload-artifact
Upload a file as a ClosedLoop document (PRD, implementation plan, feature, or template). Reads file content and uploads via MCP without consuming conversation context. Also supports creating new versions of existing documents. Triggers on: "upload artifact", "upload PRD", "upload implementation plan", "upload…
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
flo
MoFlo ticket spell - analyze and execute GitHub issues.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.