sc-report

sc-report is a skill for Claude Code, Codex from ersinkoc/security-check. It costs 16 tokens per session (2,049 once invoked), scanned A, original, MIT.

A generator for the final security assessment report after security findings have been checked. It combines verified findings, application architecture, dependency checks, scan statistics, and the security checks that ran.

In plain words
What is it for?
Use it to create SECURITY-REPORT.md from the pipeline's verified findings and supporting reports. The result includes an executive summary, detailed findings, scan statistics, and a prioritized remediation roadmap.
Why use it?
It turns separate scan results into one report that explains the main risks and what should be fixed first. It also assigns CVSS-style severity levels, a common way to describe vulnerability impact.

Skill for Claude CodeCodex

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/ersinkoc/security-check/sc-report
Any agent
npx skills add ersinkoc/security-check --skill sc-report
Clone the repo
git clone --depth 1 https://github.com/ersinkoc/security-check

Made for: Claude Code, Codex.

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 sc-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-report.svg)](https://agentmods.dev/skills/ersinkoc/security-check/sc-report)
Your own site
<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-report"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-report.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,049 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.00016 $0.02049
Opus 5 $0.00008 $0.01025
Sonnet 5 $0.00003 $0.00410
Haiku 4.5 $0.00002 $0.00205

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

Security

Grade A, and why

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

skills/sc-report/SKILL.md · 312 lines

How it starts

The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SC: Report Generator — Final Security Assessment

Purpose

Generates the final consolidated security assessment report from verified findings. Produces an executive summary, detailed findings with CVSS v3.1-style severity ratings, scan statistics, and a prioritized remediation roadmap. This is the primary deliverable of the security-check pipeline.

Activation

Runs in Phase 4 of the pipeline, after sc-verifier has completed.

Input

  • security-report/verified-findings.md
  • security-report/architecture.md
  • security-report/dependency-audit.md

Output

File: security-report/SECURITY-REPORT.md

Report Generation Process

1. Data Collection

Read all input files and extract:

  • Verified findings list with confidence scores and severity
  • Architecture summary (languages, frameworks, app type)
  • Dependency audit summary
  • Total files scanned and lines of code (from architecture.md)
  • Skills executed and their individual result counts

2. CVSS v3.1-Style Severity Mapping

Map each finding to a CVSS-aligned severity level:

Critical (CVSS 9.0-10.0):

  • Remote Code Execution with no authentication required
  • SQL Injection allowing full database access
  • Hardcoded admin credentials or private keys
  • Deserialization RCE with network-reachable endpoint
  • Authentication bypass allowing full account takeover

High (CVSS 7.0-8.9):

  • SQL Injection with limited scope
  • Stored XSS affecting all users
  • SSRF with access to internal services
  • Broken access control (IDOR) exposing sensitive data
  • Weak cryptography protecting sensitive data
  • Privilege escalation from user to admin

Medium (CVSS 4.0-6.9):

  • Reflected XSS requiring user interaction
  • CSRF on state-changing operations
  • Missing rate limiting on sensitive endpoints
  • Information disclosure (stack traces, debug info)
  • Session management weaknesses
  • Open redirect

Low (CVSS 0.1-3.9):

  • Missing security headers (clickjacking, CSP)
  • Verbose error messages with limited information
  • Outdated dependencies without known exploitable CVE
  • Best practice violations
  • Informational findings

Read the full file on GitHub · 312 lines

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 · 312 lines · 16 tokens per session scan A b964631170ee

Subscribe to this mod's changes

sc-report is a skill published in the GitHub repository ersinkoc/security-check (56 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 2,049 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens