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/andrefigueira/.context/agents-mdgit clone --depth 1 https://github.com/andrefigueira/.contextWrote 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/andrefigueira/.context/agents-md)<a href="https://agentmods.dev/instructions/andrefigueira/.context/agents-md"><img src="https://agentmods.dev/badge/instructions/andrefigueira/.context/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.00861 | $0.00861 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
.context 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 5d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md (For AI Tools Other Than Claude Code)
Research-backed entry point. Research: .context/research.md. Full methodology: .context/substrate.md.
Claude Code reads CLAUDE.md automatically. This file is for Cursor, GitHub Copilot, Windsurf, ChatGPT, and any other AI tool.
Always loaded
Two files, every time:
.context/ai-rules.md: project-wide hard constraints.context/glossary.md: terminology
Path-scoped rules
Load only when touching matching files. Full rule files live in .claude/rules/.
This table mirrors CLAUDE.md. That file is the source of truth. Keep the two in sync.
When a file matches multiple rows, load every matching rule file.
| Touching | Rule file |
|---|---|
src/api/**, src/routes/**, src/handlers/**, app/api/** |
.claude/rules/api.md |
src/auth/**, src/middleware/auth*, src/security/** |
.claude/rules/auth.md |
src/models/**, src/db/**, src/repositories/**, migrations/**, *.sql |
.claude/rules/database.md |
src/components/**, app/** (non-page), *.tsx, *.jsx, *.vue, *.svelte |
.claude/rules/ui.md |
src/app/**/page.*, src/pages/**, public/sitemap*, public/robots*, src/head/** |
.claude/rules/seo.md |
**/*.test.*, **/*.spec.*, tests/**, __tests__/** |
.claude/rules/testing.md |
Tool-specific wiring
Cursor
.cursor/rules/ with globs: frontmatter. Example:
# .cursor/rules/api.mdc
---
description: API development patterns
globs: src/api/**,src/routes/**,src/handlers/**,app/api/**
---
@.claude/rules/api.md
Repeat for each rule in the table above.
GitHub Copilot
Create .github/copilot-instructions.md for the always-loaded set:
Follow rules in .context/ai-rules.md.
Use terminology from .context/glossary.md.
For path-scoped rules, create .github/instructions/<domain>.instructions.md with applyTo: frontmatter pointing at the matching rule file.
Windsurf
.windsurfrules is not path-aware. Keep it tight. Reference the always-loaded set and the most commonly used rule file for this project:
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.
- 5d ago First seen · 88 lines · 861 tokens per session scan A 2efa40b33bdc
.context AGENTS.md is an instructions file published in the GitHub repository andrefigueira/.context (253 stars, last pushed 4mo ago), licensed MIT. It adds 861 tokens to every session, about $0.0043 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
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).
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.
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.
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.
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).