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/gabeklein/expressive-mvc/agents-mdgit clone --depth 1 https://github.com/gabeklein/expressive-mvcWrote 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/gabeklein/expressive-mvc/agents-md)<a href="https://agentmods.dev/instructions/gabeklein/expressive-mvc/agents-md"><img src="https://agentmods.dev/badge/instructions/gabeklein/expressive-mvc/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.02771 | $0.02771 |
| Opus 5 | $0.01385 | $0.01385 |
| Sonnet 5 | $0.00554 | $0.00554 |
| Haiku 4.5 | $0.00277 | $0.00277 |
Grade A, and why
expressive-mvc 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Contributor guide for AI agents working in this repository.
Overview
Expressive MVC - class-based reactive state management library. Use skills/SKILL.md and linked references to establish the intended public contract and conventions. When working on the library itself, inspect the relevant source and tests before designing or implementing changes; use the skill docs as orientation rather than as a substitute for implementation evidence.
Monorepo: bun workspaces + changesets. Install, scripts, and builds run under bun (bun install, bun run build); tests run on vitest, which executes on node (bun run test invokes it - you never call node directly). Node otherwise appears only in release.yml, where changeset publish shells to npm for the OIDC-authenticated publish.
Structure
packages/mvc - Core primitives (@expressive/mvc)
packages/react - React adapter (@expressive/react)
packages/preact - Preact adapter (@expressive/preact)
packages/router - Router built on Component (@expressive/router)
skills/ - API reference docs (also published as skills.sh skill)
examples/ - Playground of crawlable example pages (see examples/AGENTS.md)
website/ - Docs site
Commands
bun install # Install deps
bun run test # Run package test scripts (type check + vitest)
bun run build # Build all packages (bun --filter, dependency order)
Per-package: tsc --noEmit && vitest run --coverage. A root vitest run covers every package's suite at once (workspace projects).
Testing
Runner: vitest with istanbul coverage. Test config is centralized in root vitest.config.ts, which defines the workspace projects and exports suite() - per-package vitest.config.ts files are two-liners calling suite() (or suite(true) for DOM packages, which run in vitest's happy-dom environment). Coverage: every package gates statements, branches, functions, and lines at 100% via the shared coverage.thresholds - a conditional arm is either exercised by a test or deleted as dead code. The PR workflow blocks merges on these thresholds; the README badge is generated by .github/workflows/coverage.yml from measured lcov on pushes to main.
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 · 134 lines · 2,771 tokens per session scan A 1699a1b2a7bb
expressive-mvc AGENTS.md is an instructions file published in the GitHub repository gabeklein/expressive-mvc (103 stars, last pushed 15d ago), licensed MIT. It adds 2,771 tokens to every session, about $0.0139 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.