Borrowing it
Nothing to install: this file belongs to SigNoz/signoz-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SigNoz/signoz-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/SigNoz/signoz-mcp-serverWrote 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/signoz/signoz-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/signoz/signoz-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/signoz/signoz-mcp-server/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/signoz/signoz-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/signoz/signoz-mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01499 | $0.01499 |
| Opus 5 | $0.00749 | $0.00749 |
| Sonnet 5 | $0.00300 | $0.00300 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
signoz-mcp-server CLAUDE.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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Development Conventions
Consult docs/ (architecture, MCP best practices) and plans/ (per-feature context and plans) when you need background on a subsystem or an in-flight feature.
Feature Planning Convention
For every non-trivial feature, maintain a file pair in plans/ and commit it alongside the feature PR:
plans/
├── <feature>.context.md ← prompt, links, open questions, discussion log
└── <feature>.plan.md ← implementation plan
Rules
- Before implementing, check
plans/for an existing context file for the feature. - After each brainstorm exchange, append a dated entry to the discussion log in
.context.md. - When the plan changes, rewrite the relevant section in
.plan.mdand note the change with a dated entry in.context.md. - Mark open questions as resolved (with the answer inline) when they are settled in discussion.
- The discussion log in
.context.mdis append-only: never rewrite or delete prior log entries; it is the audit trail of why decisions were made. Only the Open Questions checklist may be updated in place (rule 4). .plan.mdis rewritten freely: it always reflects current thinking, not history.- Add a
## Statusline at the top of every.plan.md:Planning: actively being designedIn Progress: implementation underwayDone: shipped
File templates for both files live in plans/TEMPLATES.md.
Git & PR
- Conventional commits:
feat:,fix:,chore:,refactor:,test:,docs:. - PR titles must follow the same conventional-commit format, e.g.
chore(rate-limits): centralize override defaults. - Create GitHub issues in
SigNoz/nerve-podby default. Only use another repo when the user explicitly asks for that specific repo. - Keep PR body in sync with actual changes.
Code Style
- Avoid long inline code comments unless needed; keep comments concise and non-redundant.
Client-Visible Writing Style
When editing tool or parameter descriptions, signoz:// resources, prompts, server instructions, or manifest.json descriptions, follow docs/client-visible-writing-style.md. Skip it for code, tests, and internal docs.
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 Changed · +2 lines · +71 tokens per session 2b4ac215ecb4
- 9d ago First seen · 90 lines · 1,428 tokens per session scan A 182e81ef5c19
signoz-mcp-server CLAUDE.md is an instructions file published in the GitHub repository SigNoz/signoz-mcp-server (118 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,499 tokens to every session, about $0.0075 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
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).
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.