Borrowing it
Nothing to install: this file belongs to statuser-cloud/mcp. 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/statuser-cloud/mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/statuser-cloud/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/statuser-cloud/mcp/claude-md)<a href="https://agentmods.dev/instructions/statuser-cloud/mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/statuser-cloud/mcp/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/statuser-cloud/mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/statuser-cloud/mcp/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.00913 | $0.00913 |
| Opus 5 | $0.00456 | $0.00456 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
mcp 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 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@statuser/mcp — notes for Claude
An MCP server on top of the public Statuser API: stdio transport, hand-curated
tools over types generated from the production OpenAPI spec. Published to npm as
@statuser/mcp with provenance. This repository is public — non-public data
(internal accounts, credentials, internal addresses) and links to private
repositories never land in repo files, comments included.
Language
- Commits, PRs, branch names and code comments — English only. The repo is public and its history is read from the outside. Other repositories in this project are kept in Russian — do not carry that habit across repos.
- README and user-facing docs — Russian (that is the audience).
- Tool
description/titleand error text — English: they end up in the LLM context inside the user's client.
Never edit by hand
spec/openapi.json and src/generated/openapi.ts are output of
npm run fetch-spec (pulls /swagger-json from production). Hand edits are
overwritten by the next sync. Need different behaviour — change the API on your
side, then sync. src/generated/helpers.ts is hand-written and fine to edit.
Release cycle
sync-spec.ymlruns onrepository_dispatch: backend-deployed, sent by the API's CI after a successful production deploy, plus a safety-net cron at 06:00 UTC and a manual trigger.- If the spec changed, a
chore/sync-specPR againstmainis opened with a patch version bump. A breaking change (removed endpoint, renamed field, narrowed enum) needs a manual minor/major bump in that same PR — the auto-bump does not detect one. - After the merge the tag is pushed by hand, and the tag is what triggers
publishing:
git pull && git tag "v$(jq -r .version package.json)" && git push --tags. The version inpackage.jsonmust match the tag —publish.ymlgates on it.
Never move a published v* tag. npm refuses to republish the same version,
and provenance breaks on a moved tag. Got a release wrong — ship the next
version instead of repointing the tag.
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 · 80 lines · 913 tokens per session scan A 6e760e404a9a
mcp CLAUDE.md is an instructions file published in the GitHub repository statuser-cloud/mcp (2 stars, last pushed 5d ago), licensed MIT. It adds 913 tokens to every session, about $0.0046 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-09-09.
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).
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.
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).
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.