security-report

security-report is a command for Claude Code from bitwise-media-group/skills. It costs 30 tokens per session (207 once invoked), scanned A, original, MIT.

A command for investigating a GitHub CodeQL code-scanning finding. CodeQL is GitHub’s tool for finding possible security problems in code; the command writes a report tied to the exact commit and updates the security index.

In plain words
What is it for?
Use it to triage an open CodeQL finding, create its report, add it to the repository index, and connect that index from SECURITY.md.
Why use it?
It provides a recorded decision about whether a finding should be fixed or dismissed, while keeping code references tied to the version that was checked.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the workflow plugin — 4 skills, 2 commands shipped together

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 commands/bitwise-media-group/skills/security-report
Clone the repo
git clone --depth 1 https://github.com/bitwise-media-group/skills

Made for: Claude Code.

Or install workflow, the plugin that ships this one along with the rest of its 4 skills, 2 commands.

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

agentmods badge for security-report

README.md
[![agentmods](https://agentmods.dev/badge/commands/bitwise-media-group/skills/security-report.svg)](https://agentmods.dev/commands/bitwise-media-group/skills/security-report)
Your own site
<a href="https://agentmods.dev/commands/bitwise-media-group/skills/security-report"><img src="https://agentmods.dev/badge/commands/bitwise-media-group/skills/security-report.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 207 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00207
Opus 5 $0.00015 $0.00103
Sonnet 5 $0.00006 $0.00041
Haiku 4.5 $0.00003 $0.00021

Measured 5d ago against content hash 5d0f9394b611, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

security-report 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 5d 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.

plugins/workflow/commands/security-report.md · 22 lines

What it actually says

Security finding report

Apply the workflow-security-report skill to triage this code-scanning finding:

$ARGUMENTS

Follow the skill exactly:

  • A bare number refers to a finding in the current repository; a URL identifies the org, repo, and number.
  • Fetch the finding with gh api. If it does not exist, or is already closed (dismissed or fixed), stop and tell the user — closed findings are immutable and must not be re-triaged.
  • Anchor every code reference to the finding's commit SHA with a GitHub permalink, write the report to security/code-scanning/<n>.md, update security/code-scanning/index.md, and ensure SECURITY.md links the triage index.
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.

  1. 5d ago First seen · 22 lines · 30 tokens per session scan A 5d0f9394b611

Subscribe to this mod's changes

security-report is a command published in the GitHub repository bitwise-media-group/skills (2 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 207 once invoked, about $0.0002 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.