What is github-security-fix?

A troubleshooting skill for fixing supported security and code-quality findings in GitHub repositories, including dependency warnings, code-scanning alerts, and quality checks.

Use it to fix vulnerable dependencies, CodeQL or code-scanning alerts, and GitHub Code Quality findings, optionally as part of opening a pull request.

It provides a defined way to address these findings without manually working through each GitHub security or quality page. Secret-scanning alerts are not handled by it.

github-security-fix — Skill by Tracer-Cloud

Install

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.

agentmods

npx agentmods add skills/tracer-cloud/opensre/security_fix

Any agent

npx skills add Tracer-Cloud/opensre --skill security_fix

Clone the repo

git clone --depth 1 https://github.com/Tracer-Cloud/opensre

Made for: Claude Code, Codex.

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 480 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00063	$0.00480
Opus 5	$0.00032	$0.00240
Sonnet 5	$0.00013	$0.00096
Haiku 4.5	$0.00006	$0.00048

Measured 2d ago against content hash 22c1346280e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-security-fix 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 2d ago.

The scan reads SKILL.md. This mod also ships 8 executable files (__init__.py, context.py, errors.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

integrations/github/tools/security_fix/SKILL.md · 39 lines

What it actually says

GitHub Security And Quality Fix

Use fix_github_security_alert for GitHub security remediation requests, not github_cli or shell_run.

Rules:

Dependabot, code-scanning/CodeQL alerts, and Code Quality standard findings are supported.
Secret-scanning alerts are refused by the tool; tell the user to rotate or revoke the secret first.
For a broad repo request, omit alert_number and use alert_type="auto" so the tool selects one open supported security or quality finding by severity.
If the user says "hey fix the security issues" without a repo, omit owner and repo; the tool uses the current checkout's GitHub origin.
For GitHub /security/code-scanning pages or CodeQL/code-scanning backlog requests, pass alert_type="code_scanning".
For GitHub /security/quality pages or quality backlog requests, pass alert_type="code_quality".
The tool fixes findings itself: built-in fixers first, then an auto-detected coding agent CLI. Never add coding-agent advice, CLI names, or install commands beyond what the tool's error text already says.
If the tool returns response_text, output exactly that text and stop.
If no automatic patch is produced, keep the reply to one short line from error; do not say "next steps", add numbered options, list example commands, or ask a broad follow-up question.
Set open_pr=true only when the user asks to open, raise, create, or ship a pull request.
The tool runs one alert per call. Do not loop over multiple alerts unless the user explicitly asks to continue after the first result.
Report the result from summary, changed_files, branch_name, and pr_url.

Files

What ships with it

8 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.

Changes

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 · 39 lines · 63 tokens per session scan A 22c1346280e4

Subscribe to this mod's changes

github-security-fix is a skill published in the GitHub repository Tracer-Cloud/opensre (10,985 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 480 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-30.

Code review Security ai-sre alerting datadog grafana observability remediation

github-security-fix

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

GitHub Security And Quality Fix

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

host_bash

host_restart_service

file_inspector

edge_disk_audit

future_skill

hello-world