Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/instructions/shigechika/gws-mcp/agents-md)<a href="https://agentmods.dev/instructions/shigechika/gws-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/shigechika/gws-mcp/agents-md.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.03700 | $0.03700 |
| Opus 5 | $0.01850 | $0.01850 |
| Sonnet 5 | $0.00740 | $0.00740 |
| Haiku 4.5 | $0.00370 | $0.00370 |
Grade A, and why
gws-mcp 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 5d 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 — 297 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 buildsclapcommands dynamically. When adding a new service, you only need to register it incrates/google-workspace/src/services.rsand verify the Discovery URL pattern incrates/google-workspace/src/discovery.rs. Do NOT add new crates toCargo.tomlfor standard Google APIs.
[!NOTE] Package Manager: Use
pnpminstead ofnpmfor Node.js package management in this repository.
Build & Test
[!IMPORTANT] Test Coverage: CI runs
cargo test --workspace(ci.yml) — this fork has no codecov/coverage gate — but new or modified lines should still be covered by tests. When adding code, extract testable helper functions rather than embedding logic inmain/runwhere it's hard to unit-test. Runcargo testlocally 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 that changes Rust source or the workspace root Cargo.toml/Cargo.lock must include a changeset file (the CI policy check skips this requirement for PRs that touch no Rust/Cargo files, e.g. docs-only PRs). 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 (policy.yml) fails without a changeset when a PR changes Rust source or the workspace root Cargo.toml/Cargo.lock.
Architecture
The CLI uses a two-phase argument parsing strategy:
- Parse argv to extract the service name (e.g.,
drive) - Fetch the service's Discovery Document, build a dynamic
clap::Commandtree, then re-parse
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.
- 5d ago First seen · 297 lines · 3,700 tokens per session scan A f66d8972a45c
gws-mcp AGENTS.md is an instructions file published in the GitHub repository shigechika/gws-mcp (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 3,700 tokens to every session, about $0.0185 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.