cli AGENTS.md

Project instructions for contributing to a Rust command-line tool that connects to Google Workspace APIs. They explain the project structure, coding rules, package manager, testing, and architecture.

In plain words
What is it for?
They are for understanding how the project discovers Google APIs, where new services are registered, which package manager to use, how to build and test, and how to meet code-coverage checks.
Why use it?
They give contributors the repository-specific rules needed to add services or code without conflicting with its dynamic API design or test requirements.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/googleworkspace/cli/agents-md
Clone the repo
git clone --depth 1 https://github.com/googleworkspace/cli

Made for: Codex, OpenCode.

Per session 2,700 This file is loaded in full into every session.
When invoked 2,700 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02700 $0.02700
Opus 5 $0.01350 $0.01350
Sonnet 5 $0.00540 $0.00540
Haiku 4.5 $0.00270 $0.00270

Measured yesterday against content hash 5e64cee7455c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli AGENTS.md 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 240 lines

How it starts

The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Project Overview

gws is a Rust CLI tool for interacting with Google Workspace APIs. It dynamically generates its command surface at runtime by parsing Google Discovery Service JSON documents.

[!IMPORTANT] Dynamic Discovery: This project does NOT use generated Rust crates (e.g., google-drive3) for API interaction. Instead, it fetches the Discovery JSON at runtime and builds clap commands dynamically. When adding a new service, you only need to register it in crates/google-workspace/src/services.rs and verify the Discovery URL pattern in crates/google-workspace/src/discovery.rs. Do NOT add new crates to Cargo.toml for standard Google APIs.

[!NOTE] Package Manager: Use pnpm instead of npm for Node.js package management in this repository.

Build & Test

[!IMPORTANT] Test Coverage: The codecov/patch check requires that new or modified lines are covered by tests. When adding code, extract testable helper functions rather than embedding logic in main/run where it's hard to unit-test. Run cargo test locally and verify new branches are exercised.

cargo build          # Build in dev mode
cargo clippy -- -D warnings  # Lint check
cargo test           # Run tests

Changesets

Every PR must include a changeset file. Create one at .changeset/<descriptive-name>.md:

---
"@googleworkspace/cli": patch
---

Brief description of the change

Use patch for fixes/chores, minor for new features, major for breaking changes. The CI policy check will fail without a changeset.

Architecture

The CLI uses a two-phase argument parsing strategy:

  1. Parse argv to extract the service name (e.g., drive)
  2. Fetch the service's Discovery Document, build a dynamic clap::Command tree, then re-parse

Workspace Layout

The repository is a Cargo workspace with two crates:

Crate Package Purpose
crates/google-workspace/ google-workspace Publishable library — core types and helpers
crates/google-workspace-cli/ google-workspace-cli Binary crate — the gws CLI

Read the full file on GitHub · 240 lines

Changes

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.

  1. yesterday First seen · 240 lines · 2,700 tokens per session scan A 5e64cee7455c

Subscribe to this mod's changes

cli AGENTS.md is an instructions file published in the GitHub repository googleworkspace/cli (30,651 stars, last pushed 6d ago), licensed Apache-2.0. It adds 2,700 tokens to every session, about $0.0135 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.