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.
npx skills add ArabelaTso/Skills-4-SE --skill vulnerability-root-cause-analyzergit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/vulnerability-root-cause-analyzer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/vulnerability-root-cause-analyzer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/vulnerability-root-cause-analyzer/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.
<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/vulnerability-root-cause-analyzer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/vulnerability-root-cause-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 184 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 201 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00075 | $0.02718 |
| Opus 5 | $0.00037 | $0.01359 |
| Sonnet 5 | $0.00015 | $0.00544 |
| Haiku 4.5 | $0.00007 | $0.00272 |
Grade A, and why
vulnerability-root-cause-analyzer 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 9d 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Root Cause Analyzer
Analyze vulnerable code to identify the underlying root causes that enable security vulnerabilities.
Overview
Security vulnerabilities are symptoms of deeper issues in code design and implementation. This skill analyzes vulnerable code to identify:
- Violated assumptions - What the code assumes but doesn't verify
- Incorrect invariants - Properties that should hold but don't
- Missing checks - Validation that should exist but is absent
- Unsafe interactions - How components interact unsafely
- Design flaws - Architectural issues that enable vulnerabilities
The goal is to understand WHY the vulnerability exists, not just WHAT it is.
Root Cause Analysis Workflow
Vulnerable Code
↓
Identify Vulnerability Type
↓
Trace Attack Vector
↓
Analyze Assumptions
↓
Check Invariants
↓
Identify Missing Checks
↓
Examine Component Interactions
↓
Determine Root Cause
↓
Explain Exploitation Chain
Analysis Process
Step 1: Identify Vulnerability Type
Classify the vulnerability:
Common types:
- Buffer overflow
- SQL injection
- Cross-site scripting (XSS)
- Authentication bypass
- Privilege escalation
- Use-after-free
- Race condition
- Integer overflow
Step 2: Trace Attack Vector
Understand how an attacker exploits the vulnerability:
Questions:
- What input triggers the vulnerability?
- What operations are performed?
- What security boundary is crossed?
- What is the impact?
Step 3: Analyze Assumptions
Identify implicit assumptions in the code:
Common assumptions:
- Input is trusted
- Buffer is large enough
- Integer won't overflow
- Pointer is valid
- User is authenticated
- Data is sanitized
Check: Are these assumptions verified?
Step 4: Check Invariants
Verify properties that should always hold:
Common invariants:
- Buffer bounds respected
- Pointers valid before dereference
- Authentication required for sensitive operations
- Data sanitized before use
- Resources properly released
What ships with it
3 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.
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.
- 9d ago First seen · 500 lines · 75 tokens per session scan A f78acac11ba2
vulnerability-root-cause-analyzer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 75 tokens to every session and 2,718 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-09-03.
Other skills, from other repositories
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
trace
Trace Elixir call trees from entry points via mix xref. Use when debugging data flow, planning signature changes, or understanding how a bug reaches code.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
bim-consistency-checker
Check BIM model consistency: naming conventions, parameter completeness, spatial relationships, and data integrity across model elements.
022-root-cause-analysis
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the…