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/tompassarelli/nisp/agents-mdgit clone --depth 1 https://github.com/tompassarelli/nispWhat 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.02309 | $0.02309 |
| Opus 5 | $0.01154 | $0.01154 |
| Sonnet 5 | $0.00462 | $0.00462 |
| Haiku 4.5 | $0.00231 | $0.00231 |
Grade A, and why
nisp 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 2d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent context for nisp
Targeted at AI coding agents (Claude Code, Cursor, Codex, Aider, etc.) working on the nisp project itself — not on configs that consume nisp. For consumer-facing usage, see README.md.
What this repo is
A Racket #lang for writing Nix as s-expressions, plus the toolchain
that makes it useful: schema-driven validator, importer, LSP server,
programmatic editor.
Repo layout
.
├── main.rkt the DSL — AST nodes, surface forms, emitter
├── lang/reader.rkt #lang-reader hook
├── info.rkt Racket package metadata + version
├── validate.rkt validation library (AST walk, infer, type-check)
├── validate-cache.rkt schema loading + lazy submodule expansion
├── lsp.rkt LSP server (consumes validate)
├── edit.rkt programmatic source-edit library (set/unset)
├── cli/ per-subcommand modules; each provides `main`
│ ├── validate.rkt schema-driven .rkt validation
│ ├── extract-schema.rkt dump options tree → JSON cache
│ ├── import.rkt .nix → .rkt (calls Rust shim)
│ ├── schema.rkt query schema (lookup/children/search)
│ ├── rename.rkt rename option path across .rkt files
│ └── edit.rkt programmatic set/unset/enable-add/remove
├── bin/
│ ├── nisp dispatcher: `nisp <subcommand> [args...]`
│ └── nisp-lsp LSP launcher (separate so editors spawn by name)
├── nix-parser/ Rust crate wrapping rnix-parser
│ ├── src/main.rs parses Nix, emits JSON AST + comments
│ └── Cargo.toml cargo build --release before `nisp import` works
├── tests/ rackunit suite
│ ├── emit-test.rkt covers every AST node + surface form
│ ├── validate-test.rkt covers validation library
│ ├── edit-test.rkt covers edit primitives
│ ├── cli-test.rkt dispatcher + subcommand smoke tests
│ └── lsp-test.rkt subprocess JSON-RPC tests for nisp-lsp
└── examples/ runnable .rkt examples
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.
- 2d ago First seen · 194 lines · 2,309 tokens per session scan A 2b25b7c749a6
nisp AGENTS.md is an instructions file published in the GitHub repository tompassarelli/nisp (10 stars, last pushed 3mo ago), licensed MIT. It adds 2,309 tokens to every session, about $0.0115 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 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.