Borrowing it
Nothing to install: this file belongs to loerei/chronicle-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/loerei/chronicle-mcp/main/.agents/skills/sonar-remediation/SKILL.mdgit clone --depth 1 https://github.com/loerei/chronicle-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/skills/loerei/chronicle-mcp/sonar-remediation)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/sonar-remediation"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/sonar-remediation/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/loerei/chronicle-mcp/sonar-remediation"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/sonar-remediation.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.00026 | $0.01072 |
| Opus 5 | $0.00013 | $0.00536 |
| Sonnet 5 | $0.00005 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
sonar-remediation 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sonar Remediation & Quality Gate Workflows
Inspect, remediate, accept, and automate SonarQube/SonarCloud code quality issues across single files, PRs, or entire repositories (supports sonarcloud: and sonarqube: MCP servers).
Directives
- Safety Boundaries: NEVER delete, rename, or move standalone entrypoints, child processes, worker scripts, or dynamic IPC/service handlers.
- Preserve Public Signatures: NEVER modify exported module interfaces, public API signatures, or database schemas during Sonar remediation.
- Domain Contract Preservation (
S1854,S1481): NEVER alter returned object keys or state properties (e.g.favorite,id,status) to consume an unused variable. Safely delete the dead variable calculation instead. - Issue Verification Before Status Change: Before calling
change_sonar_issue_statusto flag"accept"or"falsepositive", MUST search the issue key usingsearch_sonar_issueswithissueStatuses: ["OPEN"]. - PR Scope Parameter: When analyzing an active PR, MUST pass
pullRequestIdorpullRequest. Omitting PR ID queries the default branch.
Query Scope Decision Matrix
| Scope | MCP Query Call |
|---|---|
| File | search_sonar_issues({ projectKey, componentKeys: ['<projectKey>:<filePath>'], issueStatuses: ['OPEN'] }) |
| Commit | git show --name-only <hash> $\rightarrow$ search_sonar_issues({ projectKey, componentKeys, inNewCodePeriod: true }) |
| Pull Request (PR) | search_sonar_issues({ projectKey, pullRequest: '<pr_id>', issueStatuses: ['OPEN'] }) |
| Branch | search_sonar_issues({ projectKey, branch: '<branch_name>', issueStatuses: ['OPEN'] }) |
| Repository | search_sonar_issues({ projectKey, issueStatuses: ['OPEN'] }) |
| File + PR | search_sonar_issues({ projectKey, pullRequest: '<pr_id>', componentKeys: ['<projectKey>:<filePath>'], issueStatuses: ['OPEN'] }) |
Issue Triage & Remediation Matrix
| Issue Category / Rule Key | Action | Requirements & Protocol |
|---|---|---|
Cognitive Complexity (S3776) |
Flag accept |
NEVER split functions solely for S3776. Structural splits require /improve-codebase-architecture. |
Deep Nesting (S2004) |
Flag accept |
Deep nesting in UI/event/search closures is intentional design. |
Theme Contrast (css:S7924) |
Flag accept |
Brand color palettes take precedence over automated WCAG checks. |
Regex Backtracking (S8786) |
Fix or Flag accept |
Simplify regex if possible; flag accept if regex is already minimal. |
| Duplications (CPD) | Fix code | Call get_duplications, inspect disk, consolidate duplicated blocks into shared helpers. |
Language Smells (S1854, S1481, etc.) |
Fix code | Follow domain-specific patterns in REFERENCE.md. |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 75 lines · 26 tokens per session scan A 7bc819e8c3b6
sonar-remediation is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 1,072 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…