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/realtimelogic/lsp-examples/agents-mdgit clone --depth 1 https://github.com/RealTimeLogic/LSP-ExamplesWrote 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/realtimelogic/lsp-examples/agents-md)<a href="https://agentmods.dev/instructions/realtimelogic/lsp-examples/agents-md"><img src="https://agentmods.dev/badge/instructions/realtimelogic/lsp-examples/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.1 | $0.04937 | $0.04937 |
| Opus 5 | $0.02469 | $0.02469 |
| Sonnet 5 | $0.00987 | $0.00987 |
| Haiku 4.5 | $0.00494 | $0.00494 |
Grade A, and why
LSP-Examples 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.
How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - BAS, Mako, and Xedge Examples
Purpose
This repository contains independent examples for the Barracuda App Server (BAS) ecosystem:
- BAS is the embedded C/C++ web and application server library.
- Mako Server is a standalone BAS runtime for desktop, server, and embedded Linux development and deployment.
- Xedge is a BAS-powered application environment commonly embedded in a product or firmware image.
- Xedge32 is the ESP32 edition of Xedge and adds ESP32 hardware APIs.
- LSP means Lua Server Pages: HTML resources that execute server-side Lua.
Examples are independent teaching applications, not one monolithic program. Keep changes scoped to the selected example and runtime.
Non-Negotiable Start Gate
Do not analyze, edit, generate, or test repository files until both of these steps are complete:
- Download and read all 11 mandatory references and skills listed below.
- Identify the selected example, its runnable app root, its target runtime, and its local instructions.
Do not continue with a partial reference set or guess an undocumented API.
Mandatory Reference Bootstrap
At the beginning of a task, create ./.agents/reference/rtl/ relative to this
file and download or refresh every file in the two tables below. Save each file
using its listed local filename. Verify that every response succeeded and every
file is non-empty; an HTML error page is not a valid reference download.
Create or update ./.agents/reference/rtl/manifest.md with:
- download date;
- source URL;
- local filename;
- any download or validation failure.
Read all downloaded references and skills before making changes. The task-specific guidance later in this file determines which skills are most important for the implementation; it does not make the other downloads optional.
If Downloading Fails
If network or filesystem restrictions block a download:
- Ask for the elevated network or filesystem permissions required to download and save the files.
- Retry after permission is granted.
- If permission is unavailable or downloading still fails, stop before modifying the repository.
- Give the user a copy-ready list of every missing file. Each item must contain
the clickable download link and exact destination path under
./.agents/reference/rtl/. - Ask the user to provide the files locally and resume only after all 11 files are accessible and non-empty.
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.
- 6d ago First seen · 449 lines · 4,937 tokens per session scan A b83cc125f1f1
LSP-Examples AGENTS.md is an instructions file published in the GitHub repository RealTimeLogic/LSP-Examples (41 stars, last pushed 13d ago), licensed MIT. It adds 4,937 tokens to every session, about $0.0247 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).
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.
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).
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.
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.
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.