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/princegupta1999/graylog-mcp/agents-mdgit clone --depth 1 https://github.com/PrinceGupta1999/graylog-mcpWrote 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/princegupta1999/graylog-mcp/agents-md)<a href="https://agentmods.dev/instructions/princegupta1999/graylog-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/princegupta1999/graylog-mcp/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.00554 | $0.00554 |
| Opus 5 | $0.00277 | $0.00277 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
graylog-mcp 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.
This is a copy
100% identical to bigquery-mcp-server CLAUDE.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Guidelines for Bun MCP Server
Implementation Rules
- See mcp.mdc at first and learn how to implement a MCP Server.
- Generate a appropriate package name and overwrite package.json
- Some examples using
setRequestHandler()to implement a tool or resource, but it's deprecated. Useserver.tool()orserver.resource()instead. - You can add a thrid party package if needed to meet the requirements.
- You can use Bun runtime features. Bun provides many built-in functions. See bun-file.mdc, bun-test.mdc, bun-glob.mdc, bun-utils.mdc
Build Commands
bun run build- Build the MCP server executablebun run show-package-name- Display the package name for installation- Install with:
cp dist/$npm_package_name $HOME/bin/
Code Style Guidelines
Imports & Organization
- Use named imports from MCP SDK:
import { McpServer, ResourceTemplate } from "@modelcontextprotocol/sdk/server/mcp.js" - Group imports by external packages first, then internal modules
TypeScript & Types
- Use Zod for parameter validation in tools and resources
- Prefer TypeScript strict mode with explicit type annotations
- Use async/await for asynchronous operations
Naming Conventions
- CamelCase for variables and functions
- PascalCase for classes and types
- Use descriptive names for resources, tools and prompts
MCP Best Practices
- Resources should be pure and not have side effects (like GET endpoints)
- Tools should handle specific actions with well-defined parameters (like POST endpoints)
- Write a enough description for tool and each parameters.
- Use ResourceTemplate for parameterized resources
- Properly handle errors in tool implementations and return isError: true
Error Handling
- Use try/catch blocks with specific error types
- Return proper error responses with descriptive messages
- Always close connections and free resources in finally blocks
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 · 59 lines · 554 tokens per session scan A d320788a053f
graylog-mcp AGENTS.md is an instructions file published in the GitHub repository PrinceGupta1999/graylog-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 554 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bigquery-mcp-server CLAUDE.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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 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.
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).