Borrowing it
Nothing to install: this file belongs to lukleh/mcp-sonarcloud. 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/lukleh/mcp-sonarcloud/main/AGENTS.mdgit clone --depth 1 https://github.com/lukleh/mcp-sonarcloudWrote 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/lukleh/mcp-sonarcloud/agents-md)<a href="https://agentmods.dev/instructions/lukleh/mcp-sonarcloud/agents-md"><img src="https://agentmods.dev/badge/instructions/lukleh/mcp-sonarcloud/agents-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/lukleh/mcp-sonarcloud/agents-md"><img src="https://agentmods.dev/badge/instructions/lukleh/mcp-sonarcloud/agents-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.00657 | $0.00657 |
| Opus 5.5 | $0.00263 | $0.00263 |
| Sonnet 5.5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
mcp-sonarcloud 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 1mo 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/mcp_sonarcloud/server.py contains the MCPServer server, request helpers, Pydantic response models, and the CLI entry point. Runtime-path resolution is isolated in src/mcp_sonarcloud/runtime_paths.py, and package metadata lives in src/mcp_sonarcloud/__init__.py. Tests are concentrated in tests/test_server.py, while README.md, DEVELOPMENT.md, and SONARCLOUD_API_SUPPORT.md document the public API surface and maintenance expectations.
Build, Test, and Development Commands
uv sync --extra devinstalls runtime and development dependencies.uv run mcp-sonarcloud --print-pathsshows the resolved config, state, and cache directories.uv run mcp-sonarcloud --write-sample-configwrites the defaultconfig.toml; add--overwriteonly when replacing it intentionally.uv run pytest -qruns the full test suite.uv run pytest tests/test_server.py -qruns the focused SonarCloud tool coverage.uv run ruff check src testsruns linting.uv run ty checkruns the type checker onsrc/.
Coding Style & Naming Conventions
Target Python 3.11+ with four-space indentation, explicit type hints, and async-first request code. Keep the current single-server-file structure unless a change is large enough to justify extraction. Use snake_case for functions, variables, and tests; use PascalCase for Pydantic models. New MCP tool parameters should continue to use pydantic.Field() descriptions with explicit valid values and concrete examples where that improves agent usability. Stack @surface_tool_errors below @mcp.tool() on every tool: since mcp 2.1 the SDK hides the text of any exception other than ToolError, and the decorator re-raises the types in ANTICIPATED_TOOL_ERRORS (ValueError, httpx.HTTPError, OSError) as ToolError so the caller sees the reason.
Testing Guidelines
Tests rely on pytest, pytest-asyncio, and pytest-httpx, so new API behavior should be covered with mocked HTTP exchanges rather than live SonarCloud calls. Update tests/test_server.py whenever request parameters, response parsing, organization scoping, or hotspot status validation changes. Prefer asserting both the outbound request shape and the structured response model.
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.
- 1mo ago Changed · +82 tokens per session 5ec9195e602f
- 1mo ago First seen · 26 lines · 575 tokens per session scan A 3f69f5967add
mcp-sonarcloud AGENTS.md is an instructions file published in the GitHub repository lukleh/mcp-sonarcloud (0 stars, last pushed 6d ago), licensed MIT. It adds 657 tokens to every session, about $0.0026 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.