Borrowing it
Nothing to install: this file belongs to gael55x/Grape. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gael55x/Grape/main/AGENTS.mdgit clone --depth 1 https://github.com/gael55x/GrapeWrote 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/gael55x/grape/agents-md)<a href="https://agentmods.dev/instructions/gael55x/grape/agents-md"><img src="https://agentmods.dev/badge/instructions/gael55x/grape/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.
<a href="https://agentmods.dev/instructions/gael55x/grape/agents-md"><img src="https://agentmods.dev/badge/instructions/gael55x/grape/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02431 | $0.02431 |
| Opus 5.5 | $0.00972 | $0.00972 |
| Sonnet 5.5 | $0.00486 | $0.00486 |
| Haiku 4.5 | $0.00243 | $0.00243 |
Grade A, and why
Grape 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 1mo 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Operating Rules
These rules apply to AI coding agents working on Grape.
Before Editing
Read these files first:
docs/v1/README.mddocs/v1/SPEC.mddocs/v1/architecture/invariants.mddocs/v1/architecture/state-machine.mddocs/v1/planning/implementation-roadmap.md- The specific domain doc for the module you will edit
If the needed behavior is not documented, update the docs before or with the implementation.
Do not implement from placeholders. If a supporting doc says what it should contain but does not define the contract, read docs/v1/SPEC.md and harden the supporting doc first.
Before adding code to an existing large file, read docs/v1/architecture/overview.md#code-modularity-standards. If the file is past the split checkpoint, split by ownership before adding another responsibility.
The current in-memory smoke harness is not a substitute for typechecking or behavioral tests. After the In-Memory Context Loop, do not add broad feature code until Project Skeleton And Tooling wires real TypeScript and test gates.
Documentation Traversal
Use docs/README.md for the top-level map and docs/v1/README.md for V1 work.
For V1 implementation, start with docs/v1/SPEC.md, then read only the folder that owns the change:
docs/v1/architecture/for system shape, state machine, and invariants.docs/v1/core/for trust, compression, storage, and security.docs/v1/contracts/for context artifact and context diff schemas.docs/v1/interfaces/for MCP and CLI contracts.docs/v1/quality/for tests and benchmarks.docs/v1/planning/for roadmap, logs, and changelogs.docs/v1/decisions/for accepted ADRs.docs/v1/examples/anddocs/v1/fixtures/for serialized examples and fixture expectations.docs/v1/legacy/alpha/for historical alpha-era documentation only. Do not treat legacy docs as current implementation input.
Do not add new V1 topic files directly under docs/v1/ unless they are canonical anchors like README.md or SPEC.md.
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.
- 1mo ago First seen · 169 lines · 2,431 tokens per session scan A 5bac3076ac01
Grape AGENTS.md is an instructions file published in the GitHub repository gael55x/Grape (11 stars, last pushed 3mo ago), licensed MIT. It adds 2,431 tokens to every session, about $0.0097 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.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.