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/harshanandak/forge/sonarcloudnpx skills add harshanandak/forge --skill sonarcloudgit clone --depth 1 https://github.com/harshanandak/forgeWhat 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.00245 | $0.01406 |
| Opus 5 | $0.00122 | $0.00703 |
| Sonnet 5 | $0.00049 | $0.00281 |
| Haiku 4.5 | $0.00024 | $0.00141 |
Grade A, and why
sonarcloud 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Authorization: Bearer $TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SonarCloud Query Command
Pull code quality data from SonarCloud. Requires SONARCLOUD_TOKEN environment variable.
Arguments
$ARGUMENTS- Query type and parameters
Query Types
| Query | Description | Example |
|---|---|---|
issues <project> |
Get open issues | /sonarcloud issues my-project |
metrics <project> |
Get code metrics | /sonarcloud metrics my-project |
gate <project> |
Quality gate status | /sonarcloud gate my-project |
health <project> |
Full health report | /sonarcloud health my-project |
pr <project> <pr#> |
PR analysis | /sonarcloud pr my-project 123 |
hotspots <project> |
Security hotspots | /sonarcloud hotspots my-project |
history <project> |
Analysis history | /sonarcloud history my-project |
Filters (append to query)
| Filter | Description | Example |
|---|---|---|
--branch <name> |
Filter by branch | --branch develop |
--severity <levels> |
Filter severity | --severity BLOCKER,CRITICAL |
--type <types> |
Filter issue type | --type BUG,VULNERABILITY |
--new-code |
Only new code issues | --new-code |
Instructions
- Parse the query from
$ARGUMENTSto determine:- Query type (issues, metrics, gate, health, pr, hotspots, history)
- Project key
- Optional filters (branch, severity, type, new-code, etc.)
- Check for
SONARCLOUD_TOKENenvironment variable. If not set, inform user. - Check for
SONARCLOUD_ORGenvironment variable or ask user for organization key. - Execute the appropriate API call against the SonarCloud REST API (see the API Reference section below for endpoints)
- Format and present results clearly:
- For issues: Group by severity/type, show file, line, message
- For metrics: Show as table with metric name and value
- For quality gate: Show pass/fail with failed conditions
- For health: Comprehensive summary with all data
- Offer follow-up actions:
- "Show issues in specific file?"
- "Get more details on a specific issue?"
- "Compare with another branch?"
What ships with it
2 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.
- 2d ago First seen · 164 lines · 245 tokens per session scan A 394d93e2cf8a
sonarcloud is a skill published in the GitHub repository harshanandak/forge (4 stars, last pushed 3d ago), licensed MIT. It adds 245 tokens to every session and 1,406 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…