pickfit

BrowseDeveloper CLIs

CTF_Agents

Multi-agent framework that classifies CTF challenges and runs bounded tools to report results.

Tested on Linux

Use it

Linux x86_64

You need first

  • System packages: libgmp-dev libmpfr-dev libmpc-dev
  • Keys or accounts: ANTHROPIC_API_KEY
  1. clone CTF_Agents repo

    rm -rf repo && git clone https://github.com/rmjohnson12/CTF_Agents.git repo
  2. pip install editable with all extras

    cd repo && pip install -e ".[all]"
  3. install optional gmpy2 and angr backends

    pip install gmpy2 angr

Check that it works

ctf-agents-check

The output should contain “Setup check complete.”.

First thing to try

ctf-agents-check

Start with ctf-agents-check.

What it does

These come from the README; pickfit didn’t check them one by one.

  • Solve authorized capture the flag challenges
    Not tested
  • Classify challenges and select specialists
    Not tested
  • Automate Hack The Box challenge workflow
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. Main function works
  4. Works offline

Good for

  • decode crypto challenge hex data
  • analyze local web challenge folder
  • decode hardware Saleae capture
  • investigate forensics repository with deleted history

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 2.6.0

Differences the test machine hit

  • README: sudo apt-get install libgmp-dev libmpfr-dev libmpc-dev for [lattice]
    In the test: pip install -e ".[all]" succeeded with prebuilt wheels and no apt step
  • README: ctf-agents-check reports solver backends and missing dependencies fail open
    In the test: pip install gmpy2 angr to turn the check's expected UNAVAILABLE lines into INSTALLED; without them the tool still exits 0 in HEURISTIC mode but reports missing backends, and live solves need an LLM provider

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.