How to route Claude Code and Cursor traffic through the gateway with Aifw

Related use cases from other repos

• Check an AI's claims about a binary before trusting them

  Turn an AI's guesses about a binary into VERIFIED or REFUTED verdicts with evidence.

  • Reverify
  • Security and science
  • Intermediate
  View prompt

  Using the reverify repo at 2akouwu/reverify, check each claim you made about <target binary> with reverify verify and its --claim JSON format. Report each claim as VERIFIED, REFUTED, or INCONCLUSIVE with the evidence bytes, and do not state any claim as fact unless the tool returned VERIFIED.

  Share Save

• Trace network input to dangerous sinks in a binary

  Find functions reachable from network reads that feed risky command or sink calls.

  • Ablation
  • Claude Code
  • Codex
  • Security and science
  • Advanced
  View prompt

  In the Ablation repo at ~/ablation, use the Network Sink Finder and Sink Arg Classifier on <binary path>, then trace taint from network sources to each reachable sink. Output a table of sink address, argument class, and taint path. Verify that every listed path has a callgraph edge chain from a recv, read, fgets, or accept call before you report it.

  Share Save

• Scope an AD assessment in the right phase order

  Use the methodology skills and /ad-scope to plan an authorized internal AD test before any tooling runs.

  • Claude AD
  • Claude Code
  • Security and science
  • Beginner
  View prompt

  Using the Claude-AD repo (ADScanPro/Claude-AD), run /ad-scope for the authorized internal domain <target-domain> and produce a written scope with the phase order and the environment constraints to check. Verify that the scope names the authorized targets and explicitly excludes anything outside the signed authorization.

  Share Save

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page