ctf-flag-verification

Validates candidate CTF flags against challenge ownership and reproducible evidence before submission.

1|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/hanmujun/hanmujun-agent-public --skill ctf-flag-verification-hanmujun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ctf-flag-verification
Source: https://github.com/hanmujun/hanmujun-agent-public/tree/main/.agents/skills/ctf-flag-verification
Command: npx skills add https://github.com/hanmujun/hanmujun-agent-public --skill ctf-flag-verification-hanmujun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Submitting an unverified flag in an authorized CTF wastes limited submission attempts and can pollute solve tracking with false positives. This Skill checks a candidate flag's format, source, challenge ownership, and duplicate submission history so only evidence-backed flags reach the submission step. ## Core Features & Use Cases - Format and Pattern Validation: Confirms the candidate matches the contest's configured flag pattern before any submission attempt. - Ownership and Evidence Checks: Verifies the flag actually belongs to the current challenge and is backed by reproducible solver evidence such as scripts or exploit output. - Duplicate Submission Detection: Reviews prior submission history to avoid re-submitting already-tried candidates. - Use Case: While solving a pwn challenge, your exploit prints a string resembling a flag. Run this verification to confirm it matches the flag pattern, belongs to the active challenge, and has not been submitted before, then receive a judgment without any automatic submission. ## Quick Start Verify whether the candidate flag I just extracted belongs to the current challenge and is safe to submit.

Frequently Asked Questions about ctf-flag-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a CTF flag before submitting it?▼

Flag verification checks the candidate against the contest flag pattern, confirms it belongs to the current challenge, reviews reproducible evidence, and scans submission history for duplicates. It returns a judgment without submitting anything.

What checks should a CTF flag go through before submission?▼

A candidate flag should pass format validation against the configured flag pattern, challenge ownership confirmation, evidence reproducibility review, and duplicate submission history checks. These steps prevent wasted attempts on wrong or repeated flags.

Does this flag verification submit the flag automatically?▼

No, the verification only returns a judgment about the candidate flag. Submission is a separate action handled elsewhere, so verification never consumes submission attempts on the contest platform.

Can flag verification detect duplicate submissions?▼

Yes, it reviews the challenge's submission history to identify candidates that were already tried. This avoids burning limited attempts on flags that previously failed or were already accepted.

When should I not rely on automated flag verification?▼

Verification depends on the configured flag pattern and available evidence records, so it cannot judge flags from contests with unknown formats or challenges lacking solver evidence. In those cases, manual review of the exploit output is needed.