RevoGrid is a customizable virtual data table component designed for spreadsheet-like interfaces and large data sets. Developers use it to build grid-based web interfaces with behavior associated with tools such as Excel.
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/revolist/revogrid/agents-mdgit clone --depth 1 https://github.com/revolist/revogridWrote 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/revolist/revogrid/agents-md)<a href="https://agentmods.dev/instructions/revolist/revogrid/agents-md"><img src="https://agentmods.dev/badge/instructions/revolist/revogrid/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 | $0.00756 | $0.00756 |
| Opus 5 | $0.00378 | $0.00378 |
| Sonnet 5 | $0.00151 | $0.00151 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
revogrid 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RevoGrid Agent Instructions
These rules are for AI coding agents working in the RevoGrid repository.
Source of truth
Use this order when answering questions or making changes:
- RevoGrid source in
src/ - RevoGrid types in
src/types/interfaces.ts,src/types/dimension.ts,src/types/selection.ts, andsrc/types/plugin.types.ts - Existing docs and demos in
docs/ - Existing tests in
e2e/andtest/
Do not invent RevoGrid APIs, events, props, plugin hooks, or Pro features.
Use RevoGrid MCP first when available
Use the hosted RevoGrid MCP endpoint:
https://mcp.rv-grid.com
If the MCP server is available in the client:
- search RevoGrid MCP before writing code
- prefer runnable examples over speculative code
- check feature availability before suggesting Pro-only capabilities
- use migration notes when changing version-specific code
- use TypeScript symbols from MCP results to validate naming and payload shape
If MCP and source disagree, trust the local source code in this repository.
How to reason about RevoGrid
- Treat TypeScript types as instruction-bearing API documentation.
- Prefer existing public examples and wrapper demos before creating new patterns.
- Preserve framework-specific conventions in React, Vue, Angular, and Svelte examples.
- Keep business logic out of render templates when a grid event, plugin, or typed config is the better fit.
- When the request mentions performance, think about virtualization, viewport math, and render churn before adding convenience abstractions.
Feature and licensing rules
- Distinguish Core vs Pro features before suggesting an implementation.
- Do not present Pro-only features as available in open-source RevoGrid.
- If a requested feature is Pro-only, say so clearly and offer the closest public fallback when possible.
Testing expectations
When behavior changes affect rendering, editing, selection, filtering, sorting, grouping, pinning, virtualization, export, or keyboard and mouse interaction, use the existing RevoGrid end-to-end suite.
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 · 67 lines · 756 tokens per session scan A 143f36f4efd6
revogrid AGENTS.md is an instructions file published in the GitHub repository revolist/revogrid (3,440 stars, last pushed today), licensed MIT. It adds 756 tokens to every session, about $0.0038 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
table AGENTS.md
AGENTS.md instructions for TanStack/table, covering agent instructions and packages that cannot be upgraded yet.
maroto AGENTS.md
Instructions for johnfercher/maroto, covering agent instructions, skills, definition of done, contributing commands and tool dependencies.
Tackl AGENTS.md
Instructions for 12-Studio/Tackl, covering agents.md, the one rule that trips agents up most, imports & aliases, writing a component and file layout & comments.
Tackl CLAUDE.md
Instructions for 12-Studio/Tackl: Instructions for Claude Code live in the tool-agnostic AGENTS.md.
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.