DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to score, dedupe, and report findings for a write-up with Blitzstrike

Turn a raw findings list into a deduplicated, CVSS-scored report with an integrity hash.

Authorization notice. Blitzstrike is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA security engineer who has a list of findings from a scan and needs a clean report for a ticket or client.

The problemSeveral findings often share one root cause, and severity scores are slow to compute by hand.

The outcomeA markdown or JSON report with one group per root cause, deterministic CVSS scores, and a SHA-256 integrity hash.

What you need first

  • Node.js (for npx) or Bun, plus an MCP-compatible agent such as Claude Code, Cursor, Codex, or Gemini CLI
  • For source audits: a local source tree you are allowed to scan
  • For live tests: written authorization for the target and a defined scope
  • Optional: FOFA_EMAIL and FOFA_KEY if you want FOFA asset search

Steps

  1. Run npx -y blitzstrike install if the MCP server is not yet registered with your agent.
  2. Give the agent your findings list in the format the tools accept.
  3. Ask the agent to call dedup_findings so findings sharing a sink, source, and CWE collapse into one group.
  4. Ask the agent to call cvss_score for each root cause using its attack vector values.
  5. Ask the agent to call generate_report with format set to markdown or json.

Prompt for your agent

Using the blitzstrike MCP server, call dedup_findings on <findings list>, then cvss_score for each group, then generate_report in <markdown or json>. Return the report with a summary and the SHA-256 integrity hash. Verify that every group has a CVSS base score and severity.

Caveat. The CVSS score is computed by the tool from the inputs you give it, so the input values still need to be judged by a person.

Share: X LinkedIn Hacker News Email Copy link

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