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/sonarcloud-ci-workflow/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/sonarcloud-ci-workflow)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/sonarcloud-ci-workflow"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/sonarcloud-ci-workflow/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/sonarcloud-ci-workflow"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/sonarcloud-ci-workflow.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.00050 | $0.00656 |
| Opus 5 | $0.00025 | $0.00328 |
| Sonnet 5 | $0.00010 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
sonarcloud-ci-workflow 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 9d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SonarCloud CI Workflow
Use this skill to configure, integrate, optimize, and troubleshoot SonarCloud CI-based analysis workflows via GitHub Actions.
Quick start
To integrate SonarCloud scanning into GitHub Actions:
- Ask for Token & Setup via CLI: Ask the user for their SonarCloud token. If provided, use GitHub CLI (
gh secret set SONAR_TOKEN --body "<token>") to automatically configure the secret for them. - Setup
sonar-project.propertiesin project root. - Setup GitHub Actions workflow
.github/workflows/sonarcloud.yml. - Disable "Automatic Analysis" in SonarCloud Administration.
Workflows
Setup & Optimization Checklist
- Setup GitHub Secret: Ask the user for their SonarCloud token and run
gh secret set SONAR_TOKEN --body "<token>"to configure the secret in GitHub. - Configure Project Properties: Create
sonar-project.properties.- Ensure
sonar.sourcesand exclusions are set to prevent false-positive duplication checks (e.g. excluding test and build files). - Always add
sonar.coverage.exclusions=**/*to bypass test coverage requirements on free plans without upgrading. - Ensure the file is saved as UTF-8 without BOM.
- Ensure
- Write Optimized Workflow: Create
.github/workflows/sonarcloud.yml.- Branch Trigger: Ensure the branch trigger (e.g.
mainormaster) matches the repository's default branch. - Static Analysis (Fast): Do NOT install dependencies. Only run checkout (
fetch-depth: 0) andSonarSource/[email protected]. DO NOT use deprecatedSonarSource/sonarcloud-github-action. - Coverage Analysis: If coverage is required, use Node caching (
cache: 'npm') and run builds before tests in monorepos. Usenpm installinstead ofnpm ciif there are native platform-specific binaries to avoid EBADPLATFORM errors.
- Branch Trigger: Ensure the branch trigger (e.g.
- Deactivate Autoscan: In SonarCloud console -> Administration -> Analysis Method, toggle OFF Automatic Analysis.
- Verify & Troubleshoot:
- For local pre-commit verification before pushing, follow the local code scan guidelines in /sonarqube-workflow.
- If the quality gate or test run fails on CI, refer to REFERENCE.md section 6 to troubleshoot common race conditions, CRLF line endings, and BOM issues.
What ships with it
1 file 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.
- 9d ago First seen · 40 lines · 50 tokens per session scan A 50837a95933c
sonarcloud-ci-workflow is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 656 once invoked, about $0.0003 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
gemini-review
Google Gemini CLI code review with Gemini 2.5 Pro, 1M token context, CI/CD integration.
squid-implement-night
Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Trigger after /squid-plan.
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.
pr-babysitter
Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes. Use when asked to "watch this PR", "fix CI", "resolve conflicts", or "address review comments". For PR metadata use pr-creator; for npm release PRs use autoship.
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
review
Review before merge. Stage-1 spec-compliance gate, then risk-selected Stage-2 review axes from the canonical set. analyst always runs, callers can pin extra always-on axes, and explicit deep review runs the full 16-axis set. Run after /test. Do NOT invoke code-qualities-assessment, doc-accuracy, golden-principles, or…