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/arismoko/buddy.nvim/agents-mdgit clone --depth 1 https://github.com/arismoko/buddy.nvimWhat 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.01277 | $0.01277 |
| Opus 5 | $0.00639 | $0.00639 |
| Sonnet 5 | $0.00255 | $0.00255 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
buddy.nvim AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
make test-integration # HTTP/SSE endpoint tests (uses curl) How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - buddy.nvim
Guidelines for AI agents working in this Neovim plugin codebase.
Project Overview
buddy.nvim is an MCP (Model Context Protocol) server for Neovim, written in Lua. It provides a bridge between AI agents and Neovim via HTTP/SSE endpoints.
Build & Test Commands
# Dependencies (required before testing)
make deps # Clone mini.nvim into deps/
make clean # Remove deps/
# Testing
make test # Run all unit tests
make test-file FILE=tests/test_tools.lua # Run single test file
make test-integration # HTTP/SSE endpoint tests (uses curl)
make test-all # Unit + integration tests
# Health check (inside Neovim)
:checkhealth buddy
Code Style Guidelines
Language & Runtime
- Language: Lua (LuaJIT)
- Runtime: Neovim's embedded Lua with
vim.uv(libuv bindings) - Testing: mini.test from mini.nvim
- LSP Config:
.luarc.jsonconfigures LuaLS with Neovim globals
Naming Conventions
| Element | Convention | Example |
|---|---|---|
| Variables/Functions | snake_case | tool_name, handle_request |
| Private functions | _snake_case | _accept, _dispatch |
| Modules/Classes | PascalCase | HTTPServer, JsonRpc |
| Constants | SCREAMING_SNAKE | MAX_BUFFER_SIZE |
Module Structure
local M = {}
local dep = require("buddy.dep") -- Core deps at top
local function _private_helper() -- Private: underscore prefix
end
---@param arg string Description
---@return table|nil result
---@return string|nil error
function M.public_api(arg) -- Public: on M table
local lazy = require("buddy.lazy") -- Lazy load optional deps
return result, nil
end
return M
Type Annotations (LuaLS/EmmyLua)
---@class ToolDefinition
---@field name string Tool identifier
---@field description string Human-readable description
---@field args table<string, {type: string, description: string}>
---@field required? string[] Required argument names
---@field run fun(args: table, context: table): table Execution function
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 · 200 lines · 1,277 tokens per session scan A b13c553d5ffe
buddy.nvim AGENTS.md is an instructions file published in the GitHub repository arismoko/buddy.nvim (23 stars, last pushed 5mo ago), licensed MIT. It adds 1,277 tokens to every session, about $0.0064 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.