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 instructions/nick2bad4u/sonarcloud-skill/agents-mdgit clone --depth 1 https://github.com/Nick2bad4u/SonarCloud-SkillWrote 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/instructions/nick2bad4u/sonarcloud-skill/agents-md)<a href="https://agentmods.dev/instructions/nick2bad4u/sonarcloud-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/nick2bad4u/sonarcloud-skill/agents-md.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.00435 | $0.00435 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
SonarCloud-Skill-Agent-Guidance 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 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.
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.
What it actually says
SonarCloud Skill Guidance
This repository packages the sonar-manage-findings Codex/open-agent skill. Keep changes focused on the root skill payload and the small repository automation needed to publish it.
Scope
- Treat
skills/sonar-manage-findings/SKILL.mdas the user-facing skill entrypoint. - Treat
skills/sonar-manage-findings/scripts/manage_sonar_findings.pyas the CLI entrypoint. - Keep helper modules in
skills/sonar-manage-findings/scripts/stdlib-only unless a dependency is explicitly justified and documented. - Keep
skills/sonar-manage-findings/agents/openai.yaml,skills/sonar-manage-findings/assets/, andskills/sonar-manage-findings/LICENSE.txtsynchronized with the packaged skill.
Security
- Never put Sonar tokens in command arguments, docs examples, logs, commits, or chat output.
- Prefer token environment variables such as
SONAR_TOKENor a caller-specified--token-env. - Use
--dry-runfirst for mutating operations that affect issues, hotspots, settings, tags, quality gates, or quality profiles. - Do not mark findings false positive, won't fix, safe, or fixed unless the surrounding code/config has actually been reviewed.
Validation
Run the narrowest useful checks after edits:
python -m compileall skills/sonar-manage-findings/scripts
npm run release:verify
For behavior changes, also run the relevant CLI command with --json against a safe repository or use --dry-run for mutations.
Style
- Prefer clear argparse surfaces and explicit error messages.
- Keep API response parsing defensive; validate external JSON before indexing nested fields.
- Keep docs examples copy-pasteable in PowerShell.
- Avoid broad repo-template changes unless the task is explicitly about repository automation or packaging.
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 · 42 lines · 435 tokens per session scan A e4ef24723128
SonarCloud-Skill-Agent-Guidance is an instructions file published in the GitHub repository Nick2bad4u/SonarCloud-Skill (1 stars, last pushed 11d ago), licensed Unlicense. It adds 435 tokens to every session, about $0.0022 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 instructions, from other repositories
copilot copilot-instructions.md
Instructions for navikt/copilot, covering copilot instructions for navikt/copilot, repository overview, nav development standards, nav principles and nav tech stack.
copilot AGENTS.md
Instructions for navikt/copilot, covering agents.md for navikt/copilot, what this repo is, efficiency rule, standard commands and conventions.
rolecraft AGENTS.md
Instructions for rolecraft-sh/rolecraft, covering rolecraft — development guidelines, ⚠️ startup checklist (read before every task), workflow, interaction rules and code style.
skills AGENTS.md
Instructions for flc1125/skills, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
skill.color-expert CLAUDE.md
Claude Code instructions for meodai/skill.color-expert, covering claude.md, project overview, architecture, no build/test/lint and editing guidelines.
claude-skills AGENTS.md
Instructions for obeone/claude-skills, covering agents.md, overview: claude agent skills stack, execution environment, key paths and release & versioning.