building-vulnerability-exception-tracking-system

building-vulnerability-exception-tracking-system is a skill for Claude Code from 26zl/cybersec-toolkit. It costs 31 tokens per session (1,505 once invoked), scanned A, original, MIT.

A system for recording cases where a known vulnerability cannot be fixed by the required deadline, including approvals, safeguards, and expiry dates.

In plain words
What is it for?
It helps build request and approval workflows, document compensating controls, track risk acceptance, and expire exceptions automatically.
Why use it?
It keeps accepted security risks visible and prevents temporary exceptions from becoming forgotten permanent gaps.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the cybersec-toolkit plugin — 197 skills, 2 hooks, 1 MCP server shipped together

Good fit It helps build request and approval workflows, document compensating controls, track risk acceptance, and expire exceptions automatically.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/26zl/cybersec-toolkit/building-vulnerability-exception-tracking-system
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 26zl/cybersec-toolkit --skill building-vulnerability-exception-tracking-system
Clone the repo
git clone --depth 1 https://github.com/26zl/cybersec-toolkit

Made for: Claude Code.

Or install cybersec-toolkit, the plugin that ships this one along with the rest of its 197 skills, 2 hooks, 1 MCP server.

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 building-vulnerability-exception-tracking-system

README.md
[![agentmods](https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/building-vulnerability-exception-tracking-system/github.svg)](https://agentmods.dev/skills/26zl/cybersec-toolkit/building-vulnerability-exception-tracking-system)
Your own site
<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/building-vulnerability-exception-tracking-system"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/building-vulnerability-exception-tracking-system/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for building-vulnerability-exception-tracking-system

Your own site · 80×15
<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/building-vulnerability-exception-tracking-system"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/building-vulnerability-exception-tracking-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,505 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.00031 $0.01505
Opus 5 $0.00015 $0.00753
Sonnet 5 $0.00006 $0.00301
Haiku 4.5 $0.00003 $0.00151

Measured 6d ago against content hash 3ec50ca329a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

building-vulnerability-exception-tracking-system 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 6d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/agent.py, scripts/process.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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/building-vulnerability-exception-tracking-system/SKILL.md · 185 lines

How it starts

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

Building Vulnerability Exception Tracking System

Overview

A vulnerability exception tracking system manages cases where vulnerabilities cannot be remediated within SLA timelines. It provides structured workflows for requesting exceptions, documenting compensating controls, obtaining risk acceptance approvals, and automatically expiring exceptions when their validity period ends. This ensures organizations maintain visibility into accepted risks while complying with frameworks like PCI DSS, SOC 2, and NIST CSF.

When to Use

  • When deploying or configuring building vulnerability exception tracking system capabilities in your environment
  • When establishing security controls aligned to compliance requirements
  • When building or improving security architecture for this domain
  • When conducting security assessments that require this implementation

Prerequisites

  • Python 3.9+ with flask, sqlalchemy, requests, jinja2
  • PostgreSQL or SQLite database
  • Email/Slack integration for approval notifications
  • Vulnerability management platform API (DefectDojo, Qualys, Tenable)

Exception Request Workflow

Exception Categories

Category Description Max Duration Approver Level
Remediation Delay Patch available but deployment blocked 30 days Team Lead + Security
No Fix Available Vendor has not released a patch 90 days Security Director
Business Critical System cannot be patched without outage 60 days VP Engineering + CISO
False Positive Finding is not a real vulnerability Permanent Security Analyst
Compensating Control Alternative mitigation in place 180 days Security Architect

Required Fields for Exception Request

exception_schema = {
    "cve_id": "CVE-2024-XXXX",
    "finding_id": "unique-finding-reference",
    "asset_hostname": "prod-db-01.corp.local",
    "severity": "high",
    "cvss_score": 8.1,
    "category": "remediation_delay",
    "justification": "Database upgrade required before patch can be applied",
    "compensating_controls": [
        "WAF rule blocking exploit pattern deployed",
        "Network segmentation restricting access to trusted VLANs only",
        "Enhanced monitoring via Splunk alert for exploitation indicators"
    ],
    "requested_expiration": "2024-06-15",
    "requestor_email": "[email protected]",
    "approver_emails": ["[email protected]", "[email protected]"],
    "risk_rating": "medium",
}

Read the full file on GitHub · 185 lines

Files

What ships with it

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

  1. 6d ago First seen · 185 lines · 31 tokens per session scan A 3ec50ca329a0

Subscribe to this mod's changes

building-vulnerability-exception-tracking-system is a skill published in the GitHub repository 26zl/cybersec-toolkit (52 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,505 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-09-03.

Related

Other skills, from other repositories

building-vulnerability-exception-tracking-system

Build a vulnerability exception and risk acceptance tracking system with approval workflows, compensating controls documentation, and expiration management.

autohandai/community-skills · 31 tokens

building-vulnerability-exception-tracking-system

Build a vulnerability exception and risk acceptance tracking system covering approval workflows, compensating controls documentation, and automatic expiration for vulnerabilities that miss SLA remediation timelines. Use when standing up a governance process for risk acceptance and exception approvals to support PCI…

Youngmaidainon/Agent-Level-Up · 67 tokens

building-vulnerability-exception-tracking-system

Build a vulnerability exception and risk acceptance tracking system with approval workflows, compensating controls documentation, and expiration management.

RobotFlow-Labs/skills-repo · 31 tokens

implementing-gdpr-data-protection-controls

The General Data Protection Regulation (EU) 2016/679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill cover.

xalgorix/xalgorix · 52 tokens

implementing-pci-dss-compliance-controls

PCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements.

xalgorix/xalgorix · 59 tokens

implementing-data-loss-prevention-with-microsoft-purview

Implements data loss prevention policies using Microsoft Purview to protect sensitive information across Exchange Online, SharePoint, OneDrive, Teams, endpoint devices, and Power BI. The analyst configures sensitivity labels with encryption and content marking, creates DLP policies using built-in and custom sensitive…

xalgorix/xalgorix · 148 tokens