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/alberto-codes/docvet/sonarqube_mcpgit clone --depth 1 https://github.com/Alberto-Codes/docvetWrote 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/alberto-codes/docvet/sonarqube_mcp)<a href="https://agentmods.dev/instructions/alberto-codes/docvet/sonarqube_mcp"><img src="https://agentmods.dev/badge/instructions/alberto-codes/docvet/sonarqube_mcp.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.1 | $0.00401 | $0.00401 |
| Opus 5 | $0.00200 | $0.00200 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
docvet 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- grafanaFastMCP sonarqube_mcp.instructions.md — 100% identical, 0 lines differ
- chains-api sonarqube_mcp.instructions.md — 100% identical, 0 lines differ
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_listtool (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_analysistool 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_analysistool if it exists.
Project Keys
- When a user mentions a project key, use
search_my_sonarqube_projectsfirst 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 authorizedoccurs, verify the token type
Project Not Found
- Use
search_my_sonarqube_projectsto 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
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.
- 2d ago First seen · 43 lines · 401 tokens per session scan A 46e092be7750
docvet sonarqube_mcp.instructions.md is an instructions file published in the GitHub repository Alberto-Codes/docvet (9 stars, last pushed 2d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
plan-forge release-checklist.instructions.md
Plan Forge release procedure — auto-loads when editing release-related files. Maintainer-only; NOT shipped to consuming projects.
coograph brutal-honesty.instructions.md
Global communication style — applies to all workspaces and conversations.
ai-pr-bot CLAUDE.md
Instructions for sgharlow/ai-pr-bot, covering claude.md, common development commands, install dependencies, development mode with hot reload and build the project.