gac: Instructions file for Codex

AGENTS.md

gac AGENTS.md is an instructions file for Codex, OpenCode from thomwebb/gac. It costs 971 tokens per session, scanned A, original, MIT.

Project-specific instructions for GAC, a Python application that connects to many AI providers. They require Python commands to run through uv, a tool that manages the project's locked dependencies, and describe how to protect user data during tests.

In plain words
What is it for?
Use them when running Python tests, linters, type checks, installs, or code that reads or writes GAC statistics and configuration files.
Why use it?
They prevent dependency mismatches and stop development or tests from changing real files containing statistics, settings, or login data. They also set rules for checking work safely.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents.

This is thomwebb/gac's own configuration. It tells Codex and OpenCode how to work on gac itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gac configures →

View source ↗ thomwebb/gac
Reuse

Borrowing it

Nothing to install: this file belongs to thomwebb/gac. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/thomwebb/gac/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/thomwebb/gac

Made for: Codex, OpenCode.

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.

agentmods badge for gac AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thomwebb/gac/agents-md/github.svg)](https://agentmods.dev/instructions/thomwebb/gac/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/thomwebb/gac/agents-md"><img src="https://agentmods.dev/badge/instructions/thomwebb/gac/agents-md/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.

agentmods 80×15 button for gac AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/thomwebb/gac/agents-md"><img src="https://agentmods.dev/badge/instructions/thomwebb/gac/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 971 This file is loaded in full into every session.
When invoked 971 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00971 $0.00971
Opus 5.5 $0.00388 $0.00388
Sonnet 5.5 $0.00194 $0.00194
Haiku 4.5 $0.00097 $0.00097

Measured 2mo ago against content hash e1748c60ea89, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gac 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 2mo 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.

AGENTS.md · 91 lines

How it starts

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

GAC — Agent Guidelines

Essential rules for AI coding agents. Detailed reference: load skills from .skills/.

uv run (NON-NEGOTIABLE)

Every Python command must go through uv run:

Always Never
uv run pytest pytest
uv run python script.py python script.py
uv run ruff check . ruff check .
uv run mypy src/ mypy src/
uv run pip install X pip install X

This project has 35+ AI provider integrations — only uv + uv.lock can resolve the dependency matrix reliably across dev, CI, and production. Vanilla tools will silently break.

For subagents: always include uv run in prompts you generate. Verify compliance before accepting output.

User Data Safety (NON-NEGOTIABLE)

NEVER touch ~/.gac* files during development or testing:

  • ~/.gac/stats.json, ~/.gac_stats.json (legacy, auto-migrated)
  • ~/.gac.env, ~/.gac/oauth/*.json

When testing code that touches stats:

#  Use tmp_path + mock the file path
with patch("gac.stats.store.STATS_FILE", tmp_path / "test.json"):
    save_stats(data)  # safe

#  NEVER call reset_stats() / save_stats() without mocking

The session-scoped isolate_stats_file fixture (tests/conftest.py) handles this automatically inside pytest only. Outside pytest, back up first: cp ~/.gac/stats.json{,.bak}.

Accidental data loss is unacceptable.

Commands

make setup              # uv venv && uv pip install -e ".[dev]"
make test               # uv run -- pytest (excludes integration)
make test-integration   # real API calls (needs API keys)
make test-cov           # coverage report → htmlcov/index.html
make lint               # ruff check + ruff format --check + prettier + markdownlint (4 tools!)
make format             # auto-fix all four
make type-check         # mypy

Run specific tests:

uv run -- pytest tests/test_cli.py                    # single file
uv run -- pytest tests/providers/test_openai.py -v    # verbose
uv run -- pytest -k "test_parse_response"             # by name

Read the full file on GitHub · 91 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. 2mo ago First seen · 91 lines · 971 tokens per session scan A e1748c60ea89

Subscribe to this mod's changes

gac AGENTS.md is an instructions file published in the GitHub repository thomwebb/gac (318 stars, last pushed 18d ago), licensed MIT. It adds 971 tokens to every session, about $0.0039 per session on Opus 5.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.

Related

gac AGENTS.md compared with instructions from other repositories

gac AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
gac AGENTS.mdthomwebb/gacInstructions file31818d agoMITA971Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode