agentmods.dev

McpServer AGENTS.md

Repository instructions for an MCP server, a service that lets coding agents call registered tools through a shared protocol. They define how agents should start work, follow source files, and record session changes.

In plain words
What is it for?
Use them when contributing to the repository, especially when bootstrapping a session, following prompt templates, calling helper modules, and updating the session log after meaningful work.
Why use it?
They prevent agents from using outdated instructions, making raw API calls, or losing important decisions and file changes between work sessions.

Instructions file for CodexOpenCode

2 11d ago A scan 1,993 tokens original Apache-2.0
View the source file sharpninja/McpServer
Install

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.

agentmods
npx agentmods add instructions/sharpninja/mcpserver/agents-md
Clone the repo
git clone --depth 1 https://github.com/sharpninja/McpServer

Made for: Codex, OpenCode.

Per session 1,993 This file is loaded in full into every session.
When invoked 1,993 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01993 $0.01993
Opus 5 $0.00996 $0.00996
Sonnet 5 $0.00399 $0.00399
Haiku 4.5 $0.00199 $0.00199

Measured yesterday against content hash 18a62a877a6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

McpServer 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 yesterday.

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.

AGENTS.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

Session Start

  1. Read AGENTS-README-FIRST.yaml in the repo root for the current API key and endpoints.
  2. For specific operational steps (session bootstrap, session log turn workflow, and helper command sequence), follow AGENTS-README-FIRST.yaml.

On every subsequent user message:

  1. Follow AGENTS-README-FIRST.yaml for specific operational instructions.
  2. Complete the user's request.

Rules

  1. templates/prompt-templates.yaml (default-marker-prompt) is the source of truth for specific agent instructions. AGENTS-README-FIRST.yaml is the rendered runtime instruction set.
  2. Keep this file focused on durable workspace policy and conventions; avoid duplicating marker-file operational procedures.
  3. Use helper modules for session log and TODO operations. Do not make raw API calls.
  4. Persist session log updates immediately after each meaningful change (turn creation, action append, decision, requirement, blocker, file/context update). Do not defer saves.
  5. Capture rich turn detail: interpretation, response, status, actions (type/status/filePath), contextList, filesModified, designDecisions, requirementsDiscovered, blockers, and relevant processing dialog.
  6. Follow workspace conventions in .github/copilot-instructions.md for build, test, and architecture guidance.
  7. Use only pwsh.exe for shell commands and script execution; do not use powershell.exe.
  8. When you need API schemas, module examples, or compliance rules, load them from docs/context/ or use context_search.
  9. Do not fabricate information. If you made a mistake, acknowledge it. Distinguish facts from speculation.
  10. Prioritize correctness over speed. Do not ship code you have not verified compiles and is logically sound.
  11. When writing session logs or other audit records, agents must identify themselves accurately using their real agent identity in Pascal-Case. Do not use placeholder, legacy, or misleading sourceType values.
  12. Never edit YAML by appending, replacing, or removing text lines. Deserialize the complete document into an object, mutate the object, serialize it, and save it. Use plugins/core/lib-ps/yaml-object-mutation.ps1 for PowerShell work.

Read the full file on GitHub · 155 lines

Changes

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.

  1. yesterday First seen · 155 lines · 1,993 tokens per session scan A 18a62a877a6d

Subscribe to this mod's changes

McpServer AGENTS.md is an instructions file published in the GitHub repository sharpninja/McpServer (2 stars, last pushed 11d ago), licensed Apache-2.0. It adds 1,993 tokens to every session, about $0.0100 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.

Data and AITestingai-agentsai-mcpai-tools
Related

Other instructions, from other repositories

ai-workflow AGENTS.md

Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.

cunhaax/ai-workflow · 2,602 tokens

trackly-cli CLAUDE.md

Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.

trackly-app/trackly-cli · 3,195 tokens

com-example-config-AsyncTestConfig

Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.

PIsberg/vibetags · 82 tokens

pupila CLAUDE.md

Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.

FranRom/pupila · 4,040 tokens

claude-bridge AGENTS.md

Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.

kadaba/claude-bridge · 1,505 tokens

UsageAtlas AGENTS.md

Instructions for SRX9/UsageAtlas, covering repository guidelines and coding approach.

SRX9/UsageAtlas · 41 tokens