vulnerability-csv-reporting

vulnerability-csv-reporting is a skill for Claude Code, Codex from xuansenpa1/skillrevise. It costs 52 tokens per session (2,864 once invoked), scanned A, original, MIT.

A reporting guide for turning vulnerability scan data into structured CSV files. CSV is a simple table format that can be opened in spreadsheet programs and processed by scripts.

In plain words
What is it for?
Use it to map vulnerability data into CSV fields, filter findings by severity, and prepare reports for spreadsheets, compliance reviews, or ticketing tools.
Why use it?
It removes the need to design security report columns and filtering rules from scratch. It helps keep vulnerability data consistent for audits, summaries, and tracking systems.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to map vulnerability data into CSV fields, filter findings by severity, and prepare reports for spreadsheets, compliance reviews, or ticketing tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xuansenpa1/skillrevise/vulnerability-csv-reporting
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.

Any agent
npx skills add xuansenpa1/skillrevise --skill vulnerability-csv-reporting
Clone the repo
git clone --depth 1 https://github.com/xuansenpa1/skillrevise

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 vulnerability-csv-reporting

README.md
[![agentmods](https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/vulnerability-csv-reporting.svg)](https://agentmods.dev/skills/xuansenpa1/skillrevise/vulnerability-csv-reporting)
Your own site
<a href="https://agentmods.dev/skills/xuansenpa1/skillrevise/vulnerability-csv-reporting"><img src="https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/vulnerability-csv-reporting.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,864 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00052 $0.02864
Opus 5 $0.00026 $0.01432
Sonnet 5 $0.00010 $0.00573
Haiku 4.5 $0.00005 $0.00286

Measured 4d ago against content hash 80c79f8543d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

vulnerability-csv-reporting 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 4d 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.

data/skillsbench/tasks/software-dependency-audit/environment/skills/vulnerability-csv-reporting/SKILL.md · 381 lines

How it starts

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

Vulnerability CSV Report Generation

This skill provides guidance on generating structured CSV reports from vulnerability scan data—a common format for security audits and compliance reporting.

Overview

CSV (Comma-Separated Values) is a widely-used format for security reports because it's:

  • Human-readable: Can be opened in Excel, Google Sheets
  • Machine-parseable: Easy to process programmatically
  • Universal: Supported by all data analysis tools
  • Lightweight: Smaller than JSON/XML formats

When to Use CSV Reports

Ideal Use Cases

  • Compliance audits requiring tabular data
  • Executive summaries for non-technical stakeholders
  • Integration with ticketing systems (Jira, ServiceNow)
  • Automated vulnerability tracking pipelines
  • Data analysis in spreadsheet tools

Limitations

  • No hierarchical data (flat structure only)
  • Limited support for nested information
  • No standard for binary data

Alternative formats: JSON (for APIs), PDF (for formal reports), HTML (for dashboards)

CSV Schema Design for Security Reports

Essential Fields

A well-designed vulnerability report CSV should include:

Field Type Description Example
Package String Vulnerable package name express
Version String Installed version 4.17.1
CVE_ID String Vulnerability identifier CVE-2022-24999
Severity Enum Risk level CRITICAL, HIGH
CVSS_Score Float/String Numeric severity score 9.8 or N/A
Fixed_Version String Patched version 4.18.0 or N/A
Title String Brief description XSS in Express.js
Url String Reference link https://nvd.nist.gov/...

Design Principles

  1. Use descriptive column names: Package not pkg, CVE_ID not id
  2. Handle missing data: Use N/A for unavailable fields, not empty strings
  3. Consistent data types: Ensure all rows have same format
  4. Include metadata: Consider adding scan date, target, tool version

Read the full file on GitHub · 381 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. 4d ago First seen · 381 lines · 52 tokens per session scan A 80c79f8543d1

Subscribe to this mod's changes

vulnerability-csv-reporting is a skill published in the GitHub repository xuansenpa1/skillrevise (55 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 2,864 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-09-03.