Common Exploit Verification

Community

HoangNguyen0403

common-exploit-verification

Enforce "No Exploit, No Report" policy with PoC construction standards, false-positive filtering, and evidence collection per vulnerability class across backend, frontend, and mobile. Use when validating security findings, constructing exploit proofs, filtering false positives, or writing pentest findings.

Overview

Publisher	HoangNguyen0403
Repository	`agent-skills-standard`
Skill name	`common-exploit-verification`
Stars	569
Forks	164
Bundled files	3
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by HoangNguyen0403 on GitHub. Read the source before you install it.

Installation

Install the Common Exploit Verification AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/common/common-exploit-verification

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git /tmp/agent-skills-standard
mkdir -p .claude/skills
cp -r /tmp/agent-skills-standard/skills/common/common-exploit-verification .claude/skills/common-exploit-verification

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Common Exploit Verification in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Common Exploit Verification on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Common Exploit Verification is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Exploit Verification Standard

Priority: P0 (CRITICAL)

Always-Apply Rules

No Exploit = No Report: Finding without reproducible PoC is discarded. No exceptions.
No Theoretical Findings: "This could be exploited if..." → rejected. Demonstrate actual impact.
No Tool Output as Evidence: Scanner output alone insufficient. Manual verification required.

PoC Construction

Every confirmed finding must include all fields:


ID: [unique identifier]
Vulnerability: [CWE-XXX: type name]
Platform: [backend|frontend|mobile-ios|mobile-android]
Component: [file:line or endpoint]
Severity: [Critical|High|Medium|Low] (CVSS: X.X)
OWASP: [mapping — e.g., A03:2021, API1:2023, M4:2024]

-- Proof of Concept --
Preconditions: [required state, auth level, config]
Steps:
1. [exact step with command/payload]
2. [expected vs actual result]
Payload: [exact input — copy-paste ready]
Evidence: [response body, status code, data returned]

-- Impact --
Impact: [what attacker gains — data, access, control]
Blast Radius: [lateral movement, escalation paths]

-- Remediation --
Fix: [specific code change, not generic advice]

Validation Gate

Result	Action	Criteria
✅ Confirmed	Include in report	PoC reproduces, impact demonstrated
⚠️ Conditional	Include with conditions	Requires specific config/timing/race
❌ Unconfirmed	Discard	Cannot reproduce despite 3 attempts
🔄 Degraded	Downgrade severity	Partial impact, mitigating controls exist

False Positive Filters

See false-positive-checklist for platform-specific filters.

Quick checks before reporting:

SAST-only finding: Is the flagged code actually reachable from user input? Trace full data flow.
Scanner noise: Does the "vulnerability" have compensating controls (WAF, middleware, framework defaults)?
Version mismatch: Is the CVE for a function the project actually uses (reachability analysis)?
Client-side only: Is the "bypass" only client-side while server enforces correctly?

Anti-Patterns

No severity inflation: Missing header ≠ Critical. CVSS score must match demonstrated impact.
No duplicate findings: Same root cause across endpoints = 1 finding with multiple affected components.
No remediation without specificity: "Use parameterized queries" → include the exact code change for the affected file.

References

False Positive Checklist — platform-specific false positive filters
Exploit Playbook — PoC templates per vulnerability class (backend, frontend, mobile)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Common Exploit Verification AI skill do?

Why use Common Exploit Verification on TypingMind?

Because you install it once and use it with any model. Common Exploit Verification is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Common Exploit Verification in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/common/common-exploit-verification. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Common Exploit Verification?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Common Exploit Verification?

As many as you like. As long as a model supports skills, you can use Common Exploit Verification with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Common Exploit Verification AI skill free?

Yes. It is published on GitHub by HoangNguyen0403 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Ruview Verify

ruvnet

CommunityPopular

Verify a RuView build — full Rust workspace tests, the deterministic Python pipeline proof (SHA-256 Trust Kill Switch), firmware hash manifest, and the ADR-028 witness bundle with one-command…

Cloud Sync

Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed…

Version Bump

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging,…

Skill Reviewer

Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Exploit Verification Standard

Priority: P0 (CRITICAL)

Always-Apply Rules

PoC Construction

Validation Gate

False Positive Filters

Anti-Patterns

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now