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/jillesca/gnmibuddy/agents-mdgit clone --depth 1 https://github.com/jillesca/gNMIBuddyWrote 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/jillesca/gnmibuddy/agents-md)<a href="https://agentmods.dev/instructions/jillesca/gnmibuddy/agents-md"><img src="https://agentmods.dev/badge/instructions/jillesca/gnmibuddy/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.00299 | $0.00299 |
| Opus 5 | $0.00150 | $0.00150 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
gNMIBuddy 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 4d 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.
What it actually says
gNMIBuddy — Project Instructions
gNMIBuddy is a Python CLI and MCP server for querying network devices via the gNMI protocol.
Operational Rules
These rules apply to all work in this repository without exception:
- Never commit files — staging is reserved for the developer's workflow
- Never push commits to any remote branch
- Never merge a PR
- To test the CLI:
uv run ...and capture output to a log file, then inspect the file - Terminal output can be cut off, so always redirect CLI command output to a log file
- Run tests with
pytestfrom the terminal — the integrated test terminal can hang - If you find improvement opportunities while working on a task, note them on the issue
- If you hit a blocker, document it in the issue thread and ask for help
Python Conventions
These apply to every Python file in this project:
- Log entries must use lazy evaluation — f-strings inside logging calls are prohibited
- Import statements must be grouped (standard library → third-party → local application), separated by blank lines, and placed at the top of each module
Coding and Design Work
When doing implementation, refactoring, code review, or object design work, load the
sw-engineering skill for the full set of engineering principles (DRY, KISS, YAGNI,
SOLID, object design, readability, and Martin Fowler's refactoring guidelines).
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.
- 4d ago First seen · 30 lines · 299 tokens per session scan A e989dc228a99
gNMIBuddy AGENTS.md is an instructions file published in the GitHub repository jillesca/gNMIBuddy (14 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 299 tokens to every session, about $0.0015 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.