agentleFS
Sign inStart free
MysterionRiseMysterionRise/ctf-kit/skills/flag/SKILL.md

flag

Skill12 starsChanged 9 months agoMITView on GitHub

Submit and validate CTF flags. Saves the flag to flag.txt, marks the challenge as solved, and validates against expected flag formats. Triggers: "submit flag", "found the flag", "flag is", "capture flag", "got the flag", "flag{", "CTF{", "picoCTF{".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this command when you:

    line 16
  2. Distinctive:

    After submitting a flag:

    line 41
  3. Distinctive:

    If in a competition, suggest moving to the next challenge

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CTF Flag

Submit and validate a CTF flag.

When to Use

Use this command when you:

  • Have found or computed a flag for a challenge
  • Want to save and validate a flag value
  • Need to mark a challenge as solved

Bundled Scripts

  • check-tools.sh — Verify ctf-kit is installed

Instructions

  1. First verify ctf-kit is available: bash scripts/check-tools.sh

  2. Submit the flag:

    ctf flag "$ARGUMENTS"
  3. Review the output:
    • Flag format validation result
    • Confirmation that flag.txt was saved
    • Challenge marked as solved in .ctf/challenge.yaml
  4. After submitting a flag:
    • Suggest /ctf-kit:status to review progress
    • Suggest /ctf-kit:writeup to generate a writeup
    • If in a competition, suggest moving to the next challenge

Options

  • --path, -p — Challenge directory (default: current directory)
  • --no-validate — Skip flag format validation

Example Usage

/ctf-kit:flag "flag{s0m3_fl4g_h3r3}"
/ctf-kit:flag "picoCTF{example_flag}" --path ./crypto/rsa-baby
/ctf-kit:flag "non_standard_flag" --no-validate

Related Commands

  • /ctf-kit:here — Set up challenge context
  • /ctf-kit:status — View challenge progress after submission
  • /ctf-kit:writeup — Generate writeup for solved challenge

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free