chains-api sonarqube_mcp.instructions.md

A set of instructions for using SonarQube, a tool that checks code for bugs, security problems, and quality issues.

In plain words
What is it for?
It helps configure SonarQube checks, find project keys, analyze changed files, and manage analysis during code changes.
Why use it?
It prevents common mistakes when choosing projects, branches, and programming languages for code analysis.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/johnaverse/chains-api/sonarqube_mcp
Clone the repo
git clone --depth 1 https://github.com/Johnaverse/chains-api

Made for: GitHub Copilot.

Per session 401 This file is loaded in full into every session.
When invoked 401 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00401 $0.00401
Opus 5 $0.00200 $0.00200
Sonnet 5 $0.00080 $0.00080
Haiku 4.5 $0.00040 $0.00040

Measured 2d ago against content hash 46e092be7750, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

chains-api sonarqube_mcp.instructions.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.

Origin

This is a copy

100% identical to grafanaFastMCP sonarqube_mcp.instructions.md — 0 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.

.github/instructions/sonarqube_mcp.instructions.md · 43 lines

What it actually says

These are some guidelines when using the SonarQube MCP server.

Important Tool Guidelines

Basic usage

  • IMPORTANT: After you finish generating or modifying any code files at the very end of the task, you MUST call the analyze_file_list tool (if it exists) to analyze the files you created or modified.
  • IMPORTANT: When starting a new task, you MUST disable automatic analysis with the toggle_automatic_analysis tool if it exists.
  • IMPORTANT: When you are done generating code at the very end of the task, you MUST re-enable automatic analysis with the toggle_automatic_analysis tool if it exists.

Project Keys

  • When a user mentions a project key, use search_my_sonarqube_projects first to find the exact project key
  • Don't guess project keys - always look them up

Code Language Detection

  • When analyzing code snippets, try to detect the programming language from the code syntax
  • If unclear, ask the user or make an educated guess based on syntax

Branch and Pull Request Context

  • Many operations support branch-specific analysis
  • If user mentions working on a feature branch, include the branch parameter

Code Issues and Violations

  • After fixing issues, do not attempt to verify them using search_sonar_issues_in_projects, as the server will not yet reflect the updates

Common Troubleshooting

Authentication Issues

  • SonarQube requires USER tokens (not project tokens)
  • When the error SonarQube answered with Not authorized occurs, verify the token type

Project Not Found

  • Use search_my_sonarqube_projects to find available projects
  • Verify project key spelling and format

Code Analysis Issues

  • Ensure programming language is correctly specified
  • Remind users that snippet analysis doesn't replace full project scans
  • Provide full file content for better analysis results
Changes

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.

  1. 2d ago First seen · 43 lines · 401 tokens per session scan A 46e092be7750

Subscribe to this mod's changes

chains-api sonarqube_mcp.instructions.md is an instructions file published in the GitHub repository Johnaverse/chains-api (5 stars, last pushed 4d ago), licensed MIT. It adds 401 tokens to every session, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to grafanaFastMCP sonarqube_mcp.instructions.md, differing in 0 lines, and is treated as a copy.