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 agentmods add instructions/thomwebb/gac/agents-mdgit clone --depth 1 https://github.com/thomwebb/gacWhat 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 | $0.00971 | $0.00971 |
| Opus 5 | $0.00485 | $0.00485 |
| Sonnet 5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
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 2d 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 — 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
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.
- 2d ago First seen · 91 lines · 971 tokens per session scan A e1748c60ea89
gac AGENTS.md is an instructions file published in the GitHub repository thomwebb/gac (318 stars, last pushed 5d ago), licensed MIT. It adds 971 tokens to every session, about $0.0049 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.
Other instructions, from other repositories
mini_agent AGENTS.md
AGENTS.md instructions for sergenes/mini_agent, covering mini agent, always, skills and tools.
mini_agent CLAUDE.md
Claude Code instructions for sergenes/mini_agent, covering mini agent, always, skills and tools.
mini_agent GEMINI.md
Gemini CLI instructions for sergenes/mini_agent: Project memory for this repo is AGENTS.md (and the matching CLAUDE.md). Follow AGENTS.md. Do not keep a second copy of those rules in this file.
Awesome-AI-Agents AGENTS.md
AGENTS.md instructions for ChatTeach/Awesome-AI-Agents, covering awesome ai agents, weekly update - 2025-04-08, supermemory, genai agents and finrobot.
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.
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).