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 commands/mukul975/threatswarm/engagegit 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/commands/mukul975/threatswarm/engage)<a href="https://agentmods.dev/commands/mukul975/threatswarm/engage"><img src="https://agentmods.dev/badge/commands/mukul975/threatswarm/engage.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.1 | $0.00019 | $0.00637 |
| Opus 5 | $0.00010 | $0.00318 |
| Sonnet 5 | $0.00004 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
engage scanned grade A with 0 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 6d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Start a new penetration testing engagement for target: $ARGUMENTS
Follow these steps in order:
-
Scope Verification: Read
scope.txtand verify that "$ARGUMENTS" is listed as an authorized target (exact IP, CIDR that includes the IP, or domain match). If NOT found in scope.txt, STOP immediately and output:❌ SCOPE VIOLATION: "$ARGUMENTS" is not in scope.txt Add the target to scope.txt before proceeding. -
Create Evidence Directories: Create the full directory structure:
mkdir -p evidence/$(date +%Y%m%d)/$ARGUMENTS/{nmap,nuclei,web,creds,screenshots,post_ex,ad,cloud,wireless,mobile,api,re,osint,network,lateral,logs} -
Print Engagement Brief:
═══════════════════════════════════════════════ ENGAGEMENT START Target: $ARGUMENTS Date: $(date -u +%Y-%m-%dT%H:%M:%SZ) Operator: $(whoami) Scope: VERIFIED ✓ Evidence: evidence/$(date +%Y%m%d)/$ARGUMENTS/ ═══════════════════════════════════════════════ -
Delegate to Recon Agent: Invoke the
reconsub-agent with the target. The recon agent will:- Run nmap TCP full scan + service/version scan
- Run nuclei CVE and exposure scans
- Run httpx for web technology detection
- Run feroxbuster for directory enumeration (if web ports found)
- Run subfinder + amass if a domain target
- Write
evidence/$(date +%Y%m%d)/$ARGUMENTS/recon_summary.md
-
Parse Recon Results: After recon completes, read
recon_summary.mdand extract:- Open ports and services with versions
- Web technologies detected
- Discovered subdomains count
-
Print Attack Vector Recommendations: Based on the recon findings, output a prioritized list:
══ RECOMMENDED ATTACK VECTORS ══════════════════ Priority 1: [e.g., "CVE-XXXX on Apache 2.4.49 (port 80)"] Priority 2: [e.g., "Default credentials on admin panel (/admin)"] Priority 3: [e.g., "SQL injection on login form"] Priority 4: [e.g., "Outdated OpenSSH — check for user enumeration"] ════════════════════════════════════════════════ Ready. Run: /project:attack $ARGUMENTS <vector>
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.
- 6d ago First seen · 57 lines · 19 tokens per session scan A e1bca763d3c3
engage is a command published in the GitHub repository mukul975/Threatswarm (77 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 637 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
recon
Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/ / directory. Usage: /recon target.com.
hunt
Active vulnerability hunting. Two-track dispatcher — asks Red Team vs WAPT, hands off to hunt-dispatch skill and sibling commands. Usage: /hunt target.com | /hunt .target.com | /hunt targets.txt [--vuln-class X] [--source-code P] [--chrome].
token-scan
Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Manual 8-class grep audit (with an optional automated scanner if present). Usage: /token-scan [--chain solana].
autopilot
Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo].
validate
Validate a finding — runs 7-Question Gate + 4-gate checklist. Kills weak findings before report writing. Prevents N/A submissions that hurt validity ratio. Usage: /validate.
triage
Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage.