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 skills/agentculture/fleet-cli/sonarclaudenpx skills add agentculture/fleet-cli --skill sonarclaudegit clone --depth 1 https://github.com/agentculture/fleet-cliWrote 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/agentculture/fleet-cli/sonarclaude)<a href="https://agentmods.dev/skills/agentculture/fleet-cli/sonarclaude"><img src="https://agentmods.dev/badge/skills/agentculture/fleet-cli/sonarclaude.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 | $0.00062 | $0.00809 |
| Opus 5 | $0.00031 | $0.00404 |
| Sonnet 5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
sonarclaude scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` — talks to the SonarCloud REST API This is a copy
100% identical to sonarclaude — 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SonarClaude
Query SonarCloud projects for quality gate status, issues, metrics, and security hotspots.
Prerequisites
The script requires the following tools on PATH:
bashcurl— talks to the SonarCloud REST APIjq— parses responses and URL-encodes accept comments
Environment
Requires SONAR_TOKEN environment variable. Set the project key per-repo via
the SONAR_PROJECT environment variable (or pass --project KEY on each
invocation).
Usage
# Quality gate status (pass/fail)
bash .claude/skills/sonarclaude/scripts/sonar.sh status
# List issues (bugs, vulnerabilities, code smells)
bash .claude/skills/sonarclaude/scripts/sonar.sh issues
# Filter issues by severity and type
bash .claude/skills/sonarclaude/scripts/sonar.sh issues --severity CRITICAL --type BUG
# Key metrics (coverage, bugs, code smells, duplication, LOC)
bash .claude/skills/sonarclaude/scripts/sonar.sh metrics
# Security hotspots
bash .claude/skills/sonarclaude/scripts/sonar.sh hotspots
# Accept (won't-fix) an OPEN issue with a rationale comment
bash .claude/skills/sonarclaude/scripts/sonar.sh accept \
--issue AZ3Ep83i4ywi8V_l99p0 \
--comment "Pushback: rule premise doesn't fit our test fixture pattern."
# Different project
bash .claude/skills/sonarclaude/scripts/sonar.sh status --project OtherOrg_OtherProject
# Raw JSON output
bash .claude/skills/sonarclaude/scripts/sonar.sh issues --raw
# Limit results
bash .claude/skills/sonarclaude/scripts/sonar.sh issues --limit 10
Options
| Flag | Default | Description |
|---|---|---|
--project |
$SONAR_PROJECT |
SonarCloud project key |
--severity |
all | Filter: BLOCKER, CRITICAL, MAJOR, MINOR, INFO |
--type |
all | Filter: BUG, VULNERABILITY, CODE_SMELL |
--limit |
25 |
Max results returned |
--raw |
off | Output raw JSON instead of formatted summary |
--issue |
— | Issue key (required for accept) |
--comment |
— | Rationale comment (required for accept) |
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.
- 3d ago First seen · 86 lines · 62 tokens per session scan A 512024e34b1d
sonarclaude is a skill published in the GitHub repository agentculture/fleet-cli (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 62 tokens to every session and 809 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to sonarclaude, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…