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 agents/invariance-ai/gps/codexgit clone --depth 1 https://github.com/invariance-ai/gpsWhat 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.00000 | $0.00879 |
| Opus 5 | $0.00000 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
codex 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex CLI
GPS gives Codex durable, symbol-anchored repo memory. Codex learns the workflow from AGENTS.md, gets structured tools through MCP, and uses the notify hook to capture durable preferences and directives after each turn.
npx -y @invariance/gps setup --yes --with-codex
Writes:
AGENTS.md— appends a<!-- gps:start -->...<!-- gps:end -->block. Codex reads this at session start and learns when to run GPS..codex/config.toml— appends a# gps:start ... # gps:endmanaged block with two entries:notify = ["npx", "-y", "@invariance/gps", "attach", "--transcript", "-"]— turn-end hook that distills the transcript into Decisions and automatically captures preferences ("from now on…", "always…", "i prefer…") and location-scoped directives[mcp_servers.gps]— registersgps serveas an MCP server
The notify hook is how Codex gets automatic preference and directive capture. It fires after every turn, reads the transcript via stdin, and persists durable instructions into the GPS memory layer according to your capture policy. You do not need to call record_preference or record_directive manually in Codex for normal "from now on" instructions; the hook handles that.
The Codex CLI does not expose pre-tool-use hooks, so the index is refreshed lazily by gps prepare and gps context calls. Treat gps like rg: a local CLI Codex runs before non-trivial edits.
Codex learns the workflow from AGENTS.md. The MCP block gives it tool access, and the notify hook captures what it should remember after each turn.
What Codex does with gps
The AGENTS.md block teaches Codex this loop:
gps prepare --intent "<what I am about to change>"
gps prepare <symbol> --intent "<short intent>"
gps brief
gps remember "<hard-won repo fact>"
gps remember "<unfinished follow-up>" --reminder --symbol <symbol>
gps lessons record "<…>"
When MCP is available, Codex can call prepare_edit, brief, get_context, tests_for, invariants_for, record_preference, and record_directive as tools. The MCP tools and CLI commands read the same .gps/ memory. Use whichever interface is more natural in the moment; the data is the same.
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 · 66 lines · 0 tokens per session scan A 20a492feebcb
codex is an agent published in the GitHub repository invariance-ai/gps (19 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 879 tokens. 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.