Borrowing it
Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. 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/AlexisBalayre/claude-code-power-config/main/.claude/skills/fix-sonar/SKILL.mdgit clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-configWrote 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/skills/alexisbalayre/claude-code-power-config/fix-sonar)<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/fix-sonar"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/fix-sonar/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/skills/alexisbalayre/claude-code-power-config/fix-sonar"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/fix-sonar.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.00024 | $0.00925 |
| Opus 5 | $0.00012 | $0.00463 |
| Sonnet 5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
fix-sonar 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 10d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SonarQube Issue Fixer
This agent automates the identification and resolution of SonarQube issues. It prioritizes high-signal mechanical fixes and structured refactoring for complex rules.
Setup: this skill talks to a SonarQube MCP server. Set
SONAR_PROJECT_KEYin.env(see.env.example) to your project's key and enable the server in.claude/settings.local.json. The fix-strategy table below encodes rule-by-rule experience from this repo — adjust the false-positive rows to match your own findings.
Operation Modes
1. Status Check (--status)
- Action: Retrieve all
OPENissues for project${SONAR_PROJECT_KEY}. - Grouping: Aggregate by Rule ID and Codebase Area (API, Frontend, Engine, Gateway, Packages).
- Display: Present a summary table showing severity, count, and affected files.
2. Parallel Resolution (--parallel)
- Batching: Group issues by Rule + Area. Create up to 3 independent batches targeting different files.
- Isolation: Dispatch 3 parallel agents with
isolation: "worktree". - Workflow: Fix ->
pnpm lint:fix->pnpm typecheck->pnpm test-> Commit -> Push -> PR. - Constraint: Never mix rules or areas within a single batch to prevent merge conflicts and context bleeding.
3. Targeted Fix (<rule> or <rule> <area>)
- Action: Resolve all instances of a specific rule, optionally restricted to a sub-directory/area.
Fix Strategy & Batching Reference
| Rule | Category | Strategy | Batch Size |
|---|---|---|---|
| S3776 | Complexity | Extract helpers, early returns, flatten nesting. | 1-2 files |
| S107 | Refactor | Group parameters into a single options object. | 1 file |
| S7763 | Export | Systematic false positive here (locally-used barrel re-exports): mark falsepositive via change_sonar_issue_status, do NOT code-fix. |
n/a |
| S6819 | React/ARIA | Systematic false positive here (custom-viz ARIA roles): mark falsepositive, do NOT code-fix. |
n/a |
| S7781 | Modern JS | Replace .replace(/x/g, y) with .replaceAll('x', y). |
5 files |
| S6606 | Nullish | Use ?? or ??= instead of || or manual checks. |
3-5 files |
| S3735 | Promises | Remove void, handle promises with .catch(). |
3-5 files |
| S6759 | React | Ensure props use the Readonly<Props> wrapper. |
3-5 files |
| S2933 | TypeScript | Add readonly modifier to class properties/members. |
5 files |
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.
- 10d ago First seen · 63 lines · 24 tokens per session scan A dac77a014206
fix-sonar is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 29d ago), licensed MIT. It adds 24 tokens to every session and 925 once invoked, about $0.0001 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-31.
Other skills, from other repositories
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
oracle
Oracle second-model review: bundle prompts/files, debug, refactor, design.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.