Borrowing it
Nothing to install: this file belongs to Elnora-AI/elnora-google-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Elnora-AI/elnora-google-workspace/main/AGENTS.mdgit clone --depth 1 https://github.com/Elnora-AI/elnora-google-workspaceWrote 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/elnora-ai/elnora-google-workspace/agents-md)<a href="https://agentmods.dev/instructions/elnora-ai/elnora-google-workspace/agents-md"><img src="https://agentmods.dev/badge/instructions/elnora-ai/elnora-google-workspace/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.00790 | $0.00790 |
| Opus 5 | $0.00395 | $0.00395 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
elnora-google-workspace 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 6d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — using the gw Google Workspace CLI
Portable rules for any coding agent (Codex, Cursor, Claude Code, …) driving this plugin. The slash commands and skills are Claude-Code-shaped, but the CLI underneath is a plain Python program you can call directly.
First run (setup)
If the CLI isn't set up yet — no .venv, no OAuth client, or gw auth status
reports token_present: false — do setup before anything else. Follow the gated
runbook in INSTALL_FOR_AGENTS.md: it builds the plugin
venv from requirements.txt, walks the user through a Google Cloud project +
Desktop OAuth client (offering to drive the browser via a Chrome DevTools MCP where
one is available), authenticates with gw auth login, and verifies a real read.
Under Claude Code the same flow is the /gw-setup command; the underlying skill is
skills/gw-setup/SKILL.md. Don't hand-roll venv or auth
steps — use those.
Invoking the CLI
- Preferred: the launcher
bin/gw(POSIX) orbin/gw.cmd/bin/gw.ps1(Windows). It finds the plugin's.venv, elsepython3/pythonon PATH. - Direct:
python3 cli/gw.py …(fall back topython cli/gw.py …). - Output is JSON on stdout, exit code
0on success. Errors are JSON on stderr with a non-zero exit. Add--compactfor minified JSON to save tokens. - Discover everything:
gw --help,gw <group> --help, andgw schema <command>for parameters, scopes, and request/response shape.gw api listshows the generic any-Google-API escape hatch.
Auth (do not reinvent)
- Setup and login are handled by
gw auth setup(machine-readable Google Cloud checklist as JSON) andgw auth login. Never hardcode or embed an OAuth client; the user supplies their own via~/.config/gw/client_secret.json,GW_CLIENT_ID/GW_CLIENT_SECRET, or--client-secret-file. - Check state with
gw auth status; list accounts withgw auth list. - Select an account per command with
--account <name>.
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.
- 6d ago First seen · 60 lines · 790 tokens per session scan A 8c0a628b91ca
elnora-google-workspace AGENTS.md is an instructions file published in the GitHub repository Elnora-AI/elnora-google-workspace (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 790 tokens to every session, about $0.0040 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-31.
Other instructions, from other repositories
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.
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 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).
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).
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.
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.