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/ricoledan/mcp-onprem-starter/agents-mdgit clone --depth 1 https://github.com/Ricoledan/mcp-onprem-starterWrote 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/ricoledan/mcp-onprem-starter/agents-md)<a href="https://agentmods.dev/instructions/ricoledan/mcp-onprem-starter/agents-md"><img src="https://agentmods.dev/badge/instructions/ricoledan/mcp-onprem-starter/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.00892 | $0.00892 |
| Opus 5 | $0.00446 | $0.00446 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
mcp-onprem-starter 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 5d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide — mcp-onprem-starter
Commands
npm run dev— run against the bundled mock upstream, zero confignpm run ci— typecheck + test + build; must pass before commitjust verify— the above, plus a cold Docker build, a non-root boot check, and a save/load rollback drilljust smoke— dependency budget check + npm pack/install/connect
Implementing an operator request
Treat the operator's business request as the source of truth for the implementation. Before changing code, identify:
- the business workflows the server must support
- the users or systems that will call each tool
- the upstream API, endpoints, authentication, and data schemas
- which operations are read-only, mutating, or destructive
- required confirmations, audit fields, and idempotency behavior
- the target deployment profile and operational constraints
For each requested tool, define its name, purpose, inputs, outputs, upstream mapping, errors, annotations, and acceptance criteria.
When the request leaves an important detail unspecified, record the gap and ask the operator for clarification. Keep assumptions explicit and avoid inventing API behavior or business rules.
The implementation is complete when the requested workflows are covered,
the tool contracts and upstream mappings are tested, security requirements
are enforced, documentation reflects the final behavior, and npm run ci
and just verify pass.
Use-case classification
Before implementation, confirm that the request fits the current primary profile: one MCP client using stdio to reach a customer-configured REST API. Classify any additional requirement that changes the transport, upstream protocol, trust boundary, or state model as separate design work.
Treat the following as architecture or roadmap triggers rather than implied template capabilities:
- OAuth or external identity-provider integration
- mTLS, proxy, or custom certificate-authority support
- non-REST upstreams such as SDKs, queues, files, or event streams
- asynchronous jobs, callbacks, or webhooks
- shared multi-client access or multi-tenant authorization
- durable write idempotency or domain-specific transaction semantics
- Kubernetes, systemd, or other host-integration packaging
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.
- 5d ago First seen · 88 lines · 892 tokens per session scan A 21cef9fa92e7
mcp-onprem-starter AGENTS.md is an instructions file published in the GitHub repository Ricoledan/mcp-onprem-starter (0 stars, last pushed 29d ago), licensed MIT. It adds 892 tokens to every session, about $0.0045 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-31.
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.