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/marianfoo/mcp-sap-docs/agents-mdgit clone --depth 1 https://github.com/marianfoo/mcp-sap-docsWrote 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/marianfoo/mcp-sap-docs/agents-md)<a href="https://agentmods.dev/instructions/marianfoo/mcp-sap-docs/agents-md"><img src="https://agentmods.dev/badge/instructions/marianfoo/mcp-sap-docs/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.01586 | $0.01586 |
| Opus 5 | $0.00793 | $0.00793 |
| Sonnet 5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00159 | $0.00159 |
Grade A, and why
mcp-sap-docs 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- abap-mcp-server AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Operational guide for agents and contributors adding or updating documentation sources in this repository.
What This Repository Does
sap-docs-mcp is an MCP server that:
- pulls documentation from git submodules under
sources/ - builds a local search corpus in
dist/data/index.json - builds SQLite FTS and embeddings (
dist/data/docs.sqlite) - serves search/fetch tools for different variants (
sap-docs,abap)
Core build/index flow:
setup.shinitializes/updates submodules (variant-aware)scripts/build-index.tsscans configured source directories and createsindex.jsonscripts/build-fts.tsbuilds BM25 index fromindex.jsonscripts/build-embeddings.tsbuilds semantic vectors
Source Onboarding Model (Important)
Adding a source is not one change in one file. A source typically needs coordinated updates in multiple places:
.gitmodules(submodule URL/path/branch)scripts/build-index.ts(SOURCESentry with indexing path + file patterns)- metadata config:
src/metadata.jsonforsap-docsprofileconfig/variants/abap.metadata.jsonif needed forabapprofile
- variant config:
config/variants/sap-docs.jsonconfig/variants/abap.json(if source should exist in ABAP variant)
setup.shsparse checkout mapping inget_sparse_paths()when only subfolders are needed- optional test/docs updates (README, tests, validation docs)
If any of these are missed, the source may clone but never be indexed, or index without usable URL generation, or only work in one variant.
Where Source Configuration Lives
1) Submodule registration
- File:
.gitmodules - Purpose: declare repository origin and local path under
sources/ - Pattern:
path = sources/<source-folder>url = https://github.com/<org>/<repo>.gitbranch = main|master|...
2) Indexing input
- File:
scripts/build-index.ts - Purpose: tells indexer exactly where docs live and which files to scan
- Structure:
SOURCES: SourceConfig[] - Required fields:
repoNameabsDir(oftenjoin("sources", "<folder>", "docs")or repo root)id(library ID used everywhere, e.g."/wdi5")name,descriptionfilePattern(**/*.md,**/*.mdx, etc.)type(markdown,jsdoc,sample)
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.
- 3d ago First seen · 184 lines · 1,586 tokens per session scan A bd2af522c0f1
mcp-sap-docs AGENTS.md is an instructions file published in the GitHub repository marianfoo/mcp-sap-docs (217 stars, last pushed 15d ago), licensed Apache-2.0. It adds 1,586 tokens to every session, about $0.0079 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.