crypto-attacker

crypto-attacker is an agent for Claude Code from mukul975/Threatswarm. It costs 86 tokens per session (3,350 once invoked), scanned B, original, MIT.

A security specialist for encryption and secure connections, including TLS, certificates, JSON Web Tokens (JWTs), RSA keys, hashes, and cryptographic protocols.

In plain words
What is it for?
Use it to audit TLS and certificates, test JWT handling, inspect cryptographic configurations, assess weak RSA keys, choose hash-cracking methods, and document evidence for security findings.
Why use it?
It helps find weaknesses in how an application protects data and verifies users, including unsafe settings and attack paths that ordinary checks may miss.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; positional $N argument.

Good fit Use it to audit TLS and certificates, test JWT handling, inspect cryptographic configurations, assess weak RSA keys, choose hash-cracking methods, and document evidence for security findings.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/mukul975/threatswarm/crypto-attacker
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/mukul975/Threatswarm

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for crypto-attacker

README.md
[![agentmods](https://agentmods.dev/badge/agents/mukul975/threatswarm/crypto-attacker/github.svg)](https://agentmods.dev/agents/mukul975/threatswarm/crypto-attacker)
Your own site
<a href="https://agentmods.dev/agents/mukul975/threatswarm/crypto-attacker"><img src="https://agentmods.dev/badge/agents/mukul975/threatswarm/crypto-attacker/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for crypto-attacker

Your own site · 80×15
<a href="https://agentmods.dev/agents/mukul975/threatswarm/crypto-attacker"><img src="https://agentmods.dev/badge/agents/mukul975/threatswarm/crypto-attacker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,350 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 3 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00086 $0.03350
Opus 5.5 $0.00034 $0.01340
Sonnet 5.5 $0.00017 $0.00670
Haiku 4.5 $0.00009 $0.00335

Measured 1mo ago against content hash c1667a0103e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

crypto-attacker scanned grade B with 3 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Downloads and executes remote codemediumSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

# curl https://$TARGET/.well-known/jwks.json | python3 -m json.tool

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

# curl https://$TARGET/.well-known/jwks.json | python3 -m json.tool

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

cert_pem = subprocess.run(
.claude/agents/crypto-attacker.md · 323 lines

How it starts

The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cybersecurity Skills (Invoke First)

Before starting cryptographic testing, invoke these skills via the Skill tool:

  • cybersecurity-skills:performing-ssl-tls-security-assessment
  • cybersecurity-skills:exploiting-jwt-algorithm-confusion-attack
  • cybersecurity-skills:testing-for-json-web-token-vulnerabilities
  • cybersecurity-skills:performing-cryptographic-audit-of-application
  • cybersecurity-skills:testing-jwt-token-security
  • cybersecurity-skills:performing-jwt-none-algorithm-attack
  • cybersecurity-skills:configuring-tls-1-3-for-secure-communications

Scope Enforcement

Verify target host and TLS endpoints are in scope.txt. Padding oracle attacks send many requests — confirm target can tolerate the load. Document all cryptographic findings with evidence of exploitability, not just misconfiguration.

TLS/SSL Assessment

mkdir -p evidence/$(date +%Y%m%d)/$TARGET/crypto/{tls,certs,hashes,jwt}

# testssl.sh — comprehensive TLS assessment
testssl.sh \
  --fast \
  --full \
  --color 0 \
  --jsonfile evidence/$(date +%Y%m%d)/$TARGET/crypto/tls/testssl.json \
  --logfile evidence/$(date +%Y%m%d)/$TARGET/crypto/tls/testssl.log \
  $TARGET:443 2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/crypto/tls/testssl_console.txt

# sslscan — alternative scanner
sslscan --no-colour $TARGET:443 2>&1 | \
  tee evidence/$(date +%Y%m%d)/$TARGET/crypto/tls/sslscan.txt

# nmap TLS scripts
nmap -p 443 \
  --script ssl-enum-ciphers,ssl-cert,ssl-dh-params,ssl-heartbleed,ssl-poodle,ssl-ccs-injection \
  $TARGET 2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/crypto/tls/nmap_ssl.txt

# openssl quick checks
echo | openssl s_client -connect $TARGET:443 -servername $TARGET 2>&1 | \
  tee evidence/$(date +%Y%m%d)/$TARGET/crypto/certs/cert_chain.txt

# Check TLS version support
for ver in ssl2 ssl3 tls1 tls1_1 tls1_2 tls1_3; do
  result=$(echo | openssl s_client -connect $TARGET:443 -$ver 2>&1 | grep -i "Protocol\|handshake\|error")
  echo "$ver: $result"
done 2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/crypto/tls/version_support.txt

# Check for weak cipher suites
openssl ciphers -v 'ALL:COMPLEMENTOFALL' | \
  grep -iE "DES|RC4|NULL|EXPORT|anon|MD5" | \
  tee evidence/$(date +%Y%m%d)/$TARGET/crypto/tls/weak_ciphers_ref.txt

Read the full file on GitHub · 323 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 323 lines · 0 tokens per session scan B c1667a0103e9

Subscribe to this mod's changes

crypto-attacker is an agent published in the GitHub repository mukul975/Threatswarm (89 stars, last pushed 5mo ago), licensed MIT. It adds 86 tokens to every session and 3,350 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 3 findings (downloads and executes remote code, makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

web3-auditor

Smart contract security auditor. Checks 10 bug classes in order of frequency (accounting desync 28%, access control 19%, incomplete path 17%, off-by-one 22% of Highs, oracle errors, ERC4626 attacks, reentrancy, flash loan oracle manipulation, signature replay, proxy/upgrade issues). Applies pre-dive kill signals…

Awarexone/Agentic-Bug-Hunter · 101 tokens

osint-collector

Delegates to this agent when the user asks about OSINT, reconnaissance, information gathering, target profiling, email harvesting, subdomain enumeration, social media recon, breach data, open source intelligence, or building a target dossier for authorized engagements.

0xSteph/pentest-ai-agents · 53 tokens

llm-redteam

Delegates to this agent when the user asks about LLM and AI system red teaming, prompt injection (direct and indirect), jailbreak techniques, RAG poisoning, model exfiltration, training data extraction, agent and tool-use abuse, MCP server exploitation, AI guardrail bypass, or red teaming a deployed…

0xSteph/pentest-ai-agents · 79 tokens

malware-analyst

Delegates to this agent when the user asks about malware analysis, reverse engineering, binary analysis, disassembly, debugging, sandbox analysis, static analysis, dynamic analysis, or suspicious file triage.

0xSteph/pentest-ai-agents · 44 tokens

compliance-mapper

Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…

0xSteph/pentest-ai-agents · 84 tokens

detection-engineer

Delegates to this agent when the user asks about detection rules, SIEM queries, threat hunting, indicator analysis, log analysis, blue team detection for specific attack techniques, or creating detection engineering content.

0xSteph/pentest-ai-agents · 45 tokens