nvim-stride: Instructions file for Codex

AGENTS.md

nvim-stride AGENTS.md is an instructions file for Codex, OpenCode from jim-at-jibba/nvim-stride. It costs 1,424 tokens per session, scanned A, original, MIT.

Development instructions for a Neovim plugin, a tool that extends the Neovim editor, covering its folder structure, layered design, tests, and when to read change proposals.

In plain words
What is it for?
They guide work on the plugin's Lua code, editor commands, public API, documentation, tests, and OpenSpec change proposals.
Why use it?
They tell coding agents where features belong and when a formal specification is required before making larger or ambiguous changes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is jim-at-jibba/nvim-stride's own configuration. It tells Codex and OpenCode how to work on nvim-stride itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nvim-stride configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jim-at-jibba/nvim-stride. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jim-at-jibba/nvim-stride/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/jim-at-jibba/nvim-stride

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for nvim-stride AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jim-at-jibba/nvim-stride/agents-md.svg)](https://agentmods.dev/instructions/jim-at-jibba/nvim-stride/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/jim-at-jibba/nvim-stride/agents-md"><img src="https://agentmods.dev/badge/instructions/jim-at-jibba/nvim-stride/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,424 This file is loaded in full into every session.
When invoked 1,424 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01424 $0.01424
Opus 5 $0.00712 $0.00712
Sonnet 5 $0.00285 $0.00285
Haiku 4.5 $0.00142 $0.00142

Measured 6d ago against content hash 6020c80af2ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

nvim-stride 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 6d 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.

AGENTS.md · 280 lines

How it starts

The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenSpec Instructions

These instructions are for AI assistants working in this project.

Always open @/openspec/AGENTS.md when the request:

  • Mentions planning or proposals (words like proposal, spec, change, plan)
  • Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
  • Sounds ambiguous and you need the authoritative spec before coding

Use @/openspec/AGENTS.md to learn:

  • How to create and apply change proposals
  • Spec format and conventions
  • Project structure and guidelines

Keep this managed block so 'openspec update' can refresh the instructions.

AGENTS.md

Guide for AI agents working on this Neovim plugin. Based on patterns from flash.nvim.

Architecture

Directory Structure

lua/
  plugin_name/        # Internal modules
    module.lua        # Feature modules
  plugin_name.lua     # Main entry point, public API, setup()
plugin/
  plugin_name.lua     # Vim commands, autocommands
tests/
  plugin_name/        # Test files per module
  minimal_init.lua    # Test harness
doc/                  # Help documentation

Layered Design

┌─────────────────────────────────┐
│  Public API (plugin_name.lua)   │  User-facing: setup(), commands
├─────────────────────────────────┤
│  Plugins/Modes                  │  Feature implementations
├─────────────────────────────────┤
│  Core Modules                   │  Business logic
├─────────────────────────────────┤
│  Utilities                      │  Helpers, low-level
└─────────────────────────────────┘

Module Pattern

-- Every module follows this structure
local M = {}
M.__index = M  -- If class-like

-- Private state
local state = {}

-- Private functions (local)
local function helper() end

-- Public methods
function M.new() end
function M:method() end

return M

Style Guide

Naming

Type Convention Example
Functions snake_case get_matches, update_state
Private funcs underscore prefix M:_update(), M:_call()
Variables snake_case match_count, win_id
Constants UPPER_CASE M.ESC, M.CR
Module table M local M = {}
Requires PascalCase local Config = require(...)

Read the full file on GitHub · 280 lines

Changes

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.

  1. 6d ago First seen · 280 lines · 1,424 tokens per session scan A 6020c80af2ab

Subscribe to this mod's changes

nvim-stride AGENTS.md is an instructions file published in the GitHub repository jim-at-jibba/nvim-stride (25 stars, last pushed 28d ago), licensed MIT. It adds 1,424 tokens to every session, about $0.0071 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.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens