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/labjp-mcp/mcp-alertmanager/agents-mdgit clone --depth 1 https://github.com/labjp-mcp/mcp-alertmanagerWrote 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/labjp-mcp/mcp-alertmanager/agents-md)<a href="https://agentmods.dev/instructions/labjp-mcp/mcp-alertmanager/agents-md"><img src="https://agentmods.dev/badge/instructions/labjp-mcp/mcp-alertmanager/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.00839 | $0.00839 |
| Opus 5 | $0.00419 | $0.00419 |
| Sonnet 5 | $0.00168 | $0.00168 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
mcp-alertmanager 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Agents.md for Alertmanager MCP Server
This Agents.md file provides comprehensive guidance for AI assistants and coding agents (like Gemini, Cursor, and others) to work with this codebase.
This repository contains the mcp-alertmanager project, a Go-based Model Context Protocol (MCP) server that provides Prometheus Alertmanager integration. This MCP server enables AI assistants to manage alerts, silences, and perform incident response using the Model Context Protocol (MCP).
Project Structure and Repository Layout
- Go package layout follows standard Go conventions:
cmd/mcp-alertmanager/- main application entry point.pkg/- libraries grouped by domain.alertmanager/- Alertmanager client and API interaction.kubernetes/- Kubernetes client management and auto-discovery.mcputil/- MCP utility functions and helpers.toolsets/- Toolset registration and management for MCP tools.version/- Version information management.
.github/- GitHub-related configuration (Actions workflows, Dependabot).build/- Build configuration files (included via Makefile).npm/- Node packages that wrap the compiled binaries for distribution through npmjs.com.Containerfile- Container image description file.Makefile- Tasks for building, formatting, and testing.
Feature Development
Implement new functionality in the Go sources under cmd/ and pkg/.
The JavaScript (npm/) directory only wraps the compiled binary for distribution (npm).
Most changes will not require touching it unless the version or packaging needs to be updated.
Adding New MCP Tools
The project uses a toolset-based architecture for organizing MCP tools:
- Tool definitions and handlers are created in
pkg/toolsets/. - Toolsets group related tools together (e.g., alert tools, silence tools, status tools).
- Each tool has a handler function that implements the tool's logic.
When adding a new tool:
- Define the tool handler function that implements the tool's logic.
- Register the tool in the appropriate toolset in
pkg/toolsets/. - If creating a new toolset, register it with the MCP server.
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 · 112 lines · 839 tokens per session scan A d794f8e0bdea
mcp-alertmanager AGENTS.md is an instructions file published in the GitHub repository labjp-mcp/mcp-alertmanager (0 stars, last pushed 6d ago), licensed MIT. It adds 839 tokens to every session, about $0.0042 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).
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.