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.
npx agentmods add agents/mukul975/threatswarm/crypto-attackergit clone --depth 1 https://github.com/mukul975/ThreatswarmWrote 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.
[](https://agentmods.dev/agents/mukul975/threatswarm/crypto-attacker)<a href="https://agentmods.dev/agents/mukul975/threatswarm/crypto-attacker"><img src="https://agentmods.dev/badge/agents/mukul975/threatswarm/crypto-attacker.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00086 | $0.03350 |
| Opus 5 | $0.00043 | $0.01675 |
| Sonnet 5 | $0.00017 | $0.00670 |
| Haiku 4.5 | $0.00009 | $0.00335 |
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 5d 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( 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-assessmentcybersecurity-skills:exploiting-jwt-algorithm-confusion-attackcybersecurity-skills:testing-for-json-web-token-vulnerabilitiescybersecurity-skills:performing-cryptographic-audit-of-applicationcybersecurity-skills:testing-jwt-token-securitycybersecurity-skills:performing-jwt-none-algorithm-attackcybersecurity-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
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.
- 5d ago First seen · 323 lines · 0 tokens per session scan B c1667a0103e9
crypto-attacker is an agent published in the GitHub repository mukul975/Threatswarm (77 stars, last pushed 4mo ago), licensed MIT. It adds 86 tokens to every session and 3,350 once invoked, about $0.0004 per session on Opus 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.
Other agents, from other repositories
token-auditor
Fast meme coin and token security auditor. Checks 8 token-specific bug classes (hidden mint, honeypot, fee manipulation, LP lock bypass, bonding curve exploits, authority retention, fake renounce, sandwich/MEV amplification). Runs tokenscanner.py for automated red flag detection. Covers EVM (Solidity) and Solana…
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…
validator
Finding validator. Runs the 7-Question Gate and 4-gate checklist on a described finding. Kills weak/theoretical findings fast before report writing. Prevents N/A submissions. Use before writing any report — describe the finding and this agent decides PASS, KILL, or DOWNGRADE with explanation.
recon-ranker
Attack surface ranking agent. Takes recon output and hunt memory, produces a prioritized attack plan. Ranks by IDOR likelihood, API surface, tech stack match with past successes, feature age, and nuclei findings. Use after recon to decide what to test first.
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.
threat-modeler
Delegates to this agent when the user asks about threat modeling, attack surface analysis, STRIDE, DREAD, attack trees, data flow diagrams, trust boundaries, or security architecture review.