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 rules/ctt062/dotfiles/global-agent-instructionsgit clone --depth 1 https://github.com/ctt062/dotfilesWhat 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.00900 | $0.00900 |
| Opus 5 | $0.00450 | $0.00450 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
global-agent-instructions 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 yesterday.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandatory first step
Before any other tools or answers, read ~/.cursor/AGENTS.md with the Read tool and follow it for the rest of this conversation.
That path is a symlink to ~/.dotfiles/home/AGENTS.md, the single source of truth for global agent policy on this machine. If the live file differs from the snapshot below, the live file wins.
Snapshot of home/AGENTS.md
Global agent instructions
Read and follow this file before doing any work. This is mandatory for every agent on this machine (Claude Code, Codex, Cursor, opencode, Grok, and any other agent harness).
home.nix installs this file for Claude (~/.claude/CLAUDE.md), Codex (~/.codex/AGENTS.md), Cursor (~/.cursor/AGENTS.md), opencode (~/.config/opencode/AGENTS.md), and Grok (~/.grok/AGENTS.md).
Rules
- Never use the em dash "—". Use plain dash "-" instead.
- Never add yourself (or any AI / agent) as a git co-author unless the user explicitly asks for it. This applies to Cursor, Claude, Codex, opencode, Grok, and every other agent identity.
- Do not pass
--trailer "Co-authored-by: ..."(or anyCo-authored-by/Co-Authored-Bytext) togit commit. - Forbidden example:
git commit --trailer "Co-authored-by: Cursor <[email protected]>". - Commit with only
-m/ HEREDOC message body. No agent attribution trailers in commits or PR bodies.
- Do not pass
- Never manually modify CHANGELOG.md files or any files marked as auto-generated.
- When making technical decisions, do not give much weight to development cost. Prefer quality, simplicity, robustness, scalability, and long-term maintainability.
- When fixing bugs, always start by reproducing the bug in an E2E setting as close as possible to how an end user would experience it, so the fix addresses the real problem.
- When end-to-end testing a product, be picky about the UI and obsess over pixel perfection. If something clearly looks off, even if it is unrelated to the current task, fix it along the way.
- Apply the same standard to engineering excellence: lint failures, test failures, and flakiness. If you see one, even if it is unrelated to the current task, fix it.
- Prefer AXI over MCP and raw vendor CLIs for the same job:
- GitHub:
gh-axi(notgh, not GitHub MCP) - Visual review artifacts:
lavish-axi - Validation / shipping gates:
no-mistakes axi ...If an AXI skill is available, follow that skill.
- GitHub:
- Before using "dynamic workflows", "ultra code", or any harness feature that immediately spawns a large swarm of subagents, explain the tradeoffs and ask the user for explicit approval.
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.
- yesterday First seen · 53 lines · 900 tokens per session scan A 12e961a715cc
global-agent-instructions is a cursor rule published in the GitHub repository ctt062/dotfiles (2 stars, last pushed 21d ago), licensed MIT. It adds 900 tokens to every session, about $0.0045 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.