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/sysdiglabs/sysdig-mcp-server/agents-mdgit clone --depth 1 https://github.com/sysdiglabs/sysdig-mcp-serverWhat 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.01576 | $0.01576 |
| Opus 5 | $0.00788 | $0.00788 |
| Sonnet 5 | $0.00315 | $0.00315 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
sysdig-mcp-server 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 2d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sysdig MCP Server – Agent Developer Handbook
This document is a comprehensive guide for an AI agent tasked with developing and maintaining the Sysdig MCP Server.
1. Project Overview
Sysdig MCP Server is a Go-based Model Context Protocol (MCP) server that exposes Sysdig Monitor platform capabilities to LLMs. It provides tools for querying Kubernetes metrics through multiple transport protocols (stdio, streamable-http, SSE). Sysdig Secure-specific tools live in the separate @sysdig/secure-mcp-server package.
1.1. Quick Facts
| Topic | Details |
|---|---|
| Purpose | Expose vetted Sysdig Monitor workflows to LLMs through MCP tools. |
| Tech Stack | Go 1.26+, mcp-go, Cobra CLI, Ginkgo/Gomega, golangci-lint, Nix. |
| Entry Point | cmd/server/main.go (Cobra CLI that wires config, Sysdig client, etc.). |
| Dev Shell | nix develop provides a consistent development environment. |
| Key Commands | just fmt, just lint, just test, just check, just update. |
2. Environment Setup
2.1. Using Nix (Recommended)
The repository uses a Nix flake to ensure a consistent development environment with all required tools.
# Enter the development shell with all tools available
nix develop
# Or, if you use direnv, allow it to load the environment
direnv allow
2.2. Required Environment Variables
The server requires API credentials to connect to the Sysdig platform.
SYSDIG_MCP_API_HOST: Sysdig instance URL (e.g.,https://us2.app.sysdig.com).SYSDIG_MCP_API_TOKEN: Sysdig API token.
For a full list of optional variables (e.g., for transport configuration), see the project's README.md.
3. Architecture
3.1. Repository Layout
.github/workflows - CI Workflows
cmd/server/ - CLI entry point, tool registration
internal/
config/ - Environment variable loading and validation
infra/
clock/ - System clock abstraction (for testing)
mcp/ - MCP server handler, transport setup, middleware
tools/ - Individual MCP tool implementations
sysdig/ - Sysdig API client (generated + extensions)
docs/ - Documentation assets
justfile - Canonical development tasks (format, lint, test, generate, update)
flake.nix - Defines the Nix development environment and its dependencies
package.nix - Defines how the package is going to be built with Nix
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.
- 2d ago First seen · 143 lines · 1,576 tokens per session scan A ec6a02213cdb
sysdig-mcp-server AGENTS.md is an instructions file published in the GitHub repository sysdiglabs/sysdig-mcp-server (13 stars, last pushed 25d ago), licensed Apache-2.0. It adds 1,576 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
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.
buildNext
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).
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.
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
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.
langchain 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.