Borrowing it
Nothing to install: this file belongs to dfirtnt/Huntable-CTI-Studio. 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/dfirtnt/Huntable-CTI-Studio/main/.cursor/skills/fix-codeql-notes/SKILL.mdgit clone --depth 1 https://github.com/dfirtnt/Huntable-CTI-StudioWrote 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/dfirtnt/huntable-cti-studio/fix-codeql-notes)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/fix-codeql-notes"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/fix-codeql-notes.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.02114 |
| Opus 5 | $0.00039 | $0.01057 |
| Sonnet 5 | $0.00015 | $0.00423 |
| Haiku 4.5 | $0.00008 | $0.00211 |
Grade A, and why
fix-codeql-notes 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 7d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix CodeQL Notes (Unused Imports / Variables)
Resolves the following CodeQL rule IDs — all note severity, all mechanical fixes:
| Rule ID | What triggers it |
|---|---|
py/unused-import |
import X or from M import X where X is never referenced |
py/repeated-import |
The same module imported twice (second import is redundant) |
py/unused-local-variable |
A local variable is assigned but its value is never read |
py/unused-global-variable |
A module-level variable is defined but never referenced |
Step 0 — Gather the alert list
Pull the current open alerts from GitHub (do not guess):
gh api repos/{owner}/{repo}/code-scanning/alerts \
--paginate \
-q '.[] | select(.state=="open") | select(.rule.id | test("py/unused-import|py/repeated-import|py/unused-local-variable|py/unused-global-variable")) | {rule: .rule.id, file: .most_recent_instance.location.path, start_line: .most_recent_instance.location.start_line, message: .most_recent_instance.message.text}'
Group alerts by file. Process one file at a time (read → edit → verify).
Step 1 — For each file: Read it, then apply the right fix
Read the full file before editing anything. Understand context — an unused name might be inside a try/except guard, a TYPE_CHECKING block, or __all__.
Rule: py/unused-import and py/repeated-import
Fix decision tree (in order):
- Is the import in
__all__? → Keep it. Not a real unused import; CodeQL can be wrong here. - Is the import inside
if TYPE_CHECKING:block? → Keep it; it exists only for type annotations. - Is the import in a
try/except ImportErrorguard and is it truly never referenced anywhere in the file? → Delete the entirefrom M import Xline (or the name from a multi-name import). - Repeated import (
py/repeated-import): Delete whichever occurrence is farther from the actual use site. Typically the earlier one is the stale copy. - Plain unused import with no special context: Delete the import line. If it's part of a multi-name import (
from M import A, B, C), remove only the unused names; reformat the line if it becomes a single name.
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.
- 7d ago First seen · 150 lines · 77 tokens per session scan A 4c344d356e6a
fix-codeql-notes is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 2,114 once invoked, about $0.0004 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.
Other skills, from other repositories
analyzing-slack-space-and-file-system-artifacts
Examine file system slack space, MFT entries, USN journal, and alternate data streams to recover hidden data and reconstruct file activity on NTFS volumes.
building-detection-rule-with-splunk-spl
Build effective detection rules using Splunk Search Processing Language (SPL) correlation searches to identify security threats in SOC environments.
analyzing-supply-chain-malware-artifacts
Investigate supply chain attack artifacts including trojanized software updates, compromised build pipelines, and sideloaded dependencies to identify intrusion vectors and scope of compromise.
configuring-windows-event-logging-for-detection
Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and object access to feed SIEM detection rules. Activates for requests involving…
ctf-rev
Use when solving a CTF reverse engineering challenge — stripped binaries, packed binaries, anti-debug, custom VMs, .NET/Java decomp, Android dex, obfuscated JS, ELF/PE/Mach-O analysis. Provides workflow and tool ordering from the reversing module. Triggers on "ctf rev", "reversing", "reverse engineer", "decompile"…
ctf-pwn
Use when solving binary exploitation / pwn CTF challenges — buffer overflows, ROP, format strings, heap, kernel pwn. Provides a decision tree, exploit primitive catalog, and uses pwntools via the runscript(venv="pwntools") MCP path. Triggers on "ctf pwn", "binary exploit", "rop", "buffer overflow", "format string"…