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-pattern-matchergit 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-pattern-matcher)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/vulnerability-pattern-matcher"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/vulnerability-pattern-matcher/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-pattern-matcher"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/vulnerability-pattern-matcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Server-Side Request Forgery · line 307 Code accesses a cloud instance metadata endpoint (e.g. 169.254.169.254). A single request can return temporary IAM credentials, making this a high-value SSRF target for credential theft.Fix: Remove access to cloud metadata endpoints unless strictly required. If metadata is needed, restrict it (e.g. IMDSv2 with hop limit) and never expose returned credentials.
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.00066 | $0.02396 |
| Opus 5 | $0.00033 | $0.01198 |
| Sonnet 5 | $0.00013 | $0.00479 |
| Haiku 4.5 | $0.00007 | $0.00240 |
Grade B, and why
vulnerability-pattern-matcher scanned grade B with 2 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.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
Application makes HTTP requests to user-controlled URLs. Attacker can access internal services, cloud metadata endpoints (169.254.169.254), or perform port scanning of internal network. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get(url) How it starts
The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Pattern Matcher
Overview
This skill detects security vulnerabilities by matching code against a comprehensive database of known vulnerability patterns, insecure coding idioms, and historical CVE-style patterns. It identifies risky code, explains why each pattern is dangerous, assesses exploitability conditions, and provides severity ratings with confidence levels.
Detection Workflow
Follow these steps to detect and assess vulnerabilities:
1. Analyze Code Structure
Identify key security-relevant elements:
- User input sources (request parameters, form data, file uploads)
- Data sinks (database queries, file operations, command execution)
- Authentication and authorization mechanisms
- Cryptographic operations
- Network communications
- File and resource handling
Map data flow:
- Trace user input through the application
- Identify where untrusted data reaches sensitive operations
- Note any validation or sanitization applied
2. Match Vulnerability Patterns
Scan for known patterns:
- Injection vulnerabilities (SQL, NoSQL, LDAP, XSS, command injection)
- Authentication issues (hardcoded credentials, weak session management)
- Cryptographic failures (weak algorithms, insecure random numbers)
- Access control problems (IDOR, missing authorization)
- Deserialization vulnerabilities
- Path traversal and file inclusion
- SSRF and XXE
- Buffer overflows and memory safety
- Race conditions
For each match:
- Identify the specific pattern
- Note the exact code location
- Determine the vulnerability category
3. Assess Exploitability
For each detected vulnerability, evaluate:
Attack Complexity:
- Low: Simple exploit, no special conditions required
- Medium: Requires specific conditions, timing, or configuration
- High: Complex exploit chain, rare conditions, or significant obstacles
Privileges Required:
- None: Unauthenticated attacker can exploit
- Low: Basic user account needed
- High: Administrative or privileged access required
What ships with it
2 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 · 416 lines · 66 tokens per session scan B cc7085437298
vulnerability-pattern-matcher is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 66 tokens to every session and 2,396 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (cloud metadata endpoint, makes network calls). 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…