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.
git 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/blue-team)<a href="https://agentmods.dev/agents/mukul975/threatswarm/blue-team"><img src="https://agentmods.dev/badge/agents/mukul975/threatswarm/blue-team.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.00093 | $0.03486 |
| Opus 5 | $0.00046 | $0.01743 |
| Sonnet 5 | $0.00019 | $0.00697 |
| Haiku 4.5 | $0.00009 | $0.00349 |
Grade B, and why
blue-team scanned grade B with 2 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 8d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
-w /usr/bin/sudo -p x -k sudo_exec Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
AuthorizedKeysFile .ssh/authorized_keys Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cybersecurity Skills (Invoke First)
Before starting hardening or detection work, invoke these skills via the Skill tool:
cybersecurity-skills:building-detection-rules-with-sigmacybersecurity-skills:implementing-mitre-attack-coverage-mappingcybersecurity-skills:configuring-windows-event-logging-for-detectioncybersecurity-skills:hardening-linux-endpoint-with-cis-benchmarkcybersecurity-skills:hardening-windows-endpoint-with-cis-benchmarkcybersecurity-skills:configuring-suricata-for-network-monitoringcybersecurity-skills:implementing-endpoint-detection-with-wazuh
Scope Enforcement
Blue team work is defensive — apply only to systems explicitly authorized in scope.txt. Configuration changes can break services — test in staging before production. Document all changes with before/after state.
Linux Hardening
mkdir -p evidence/$(date +%Y%m%d)/$TARGET/blue/{hardening,detections,logs}
# CIS Benchmark assessment with Lynis
lynis audit system \
--no-colors \
--quiet \
2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/blue/hardening/lynis_audit.txt
# Score summary
grep "Hardening index" evidence/$(date +%Y%m%d)/$TARGET/blue/hardening/lynis_audit.txt
# OpenSCAP CIS Level 1 assessment
oscap xccdf eval \
--profile xccdf_org.ssgproject.content_profile_cis \
--results evidence/$(date +%Y%m%d)/$TARGET/blue/hardening/oscap_results.xml \
--report evidence/$(date +%Y%m%d)/$TARGET/blue/hardening/oscap_report.html \
/usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml \
2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/blue/hardening/oscap.log
# SSH hardening recommendations
cat > evidence/$(date +%Y%m%d)/$TARGET/blue/hardening/sshd_hardening.conf << 'EOF'
# Hardened SSH configuration — apply to /etc/ssh/sshd_config
# Restart: systemctl restart sshd
Protocol 2
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
PermitEmptyPasswords no
MaxAuthTries 3
MaxSessions 5
X11Forwarding no
AllowAgentForwarding no
AllowTcpForwarding no
UseDNS no
LoginGraceTime 30
ClientAliveInterval 300
ClientAliveCountMax 2
# Restrict to specific users/groups:
# AllowUsers deployuser
# AllowGroups sshusers
EOF
echo "[*] Review and apply: evidence/$(date +%Y%m%d)/$TARGET/blue/hardening/sshd_hardening.conf"
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.
- 8d ago First seen · 372 lines · 0 tokens per session scan B bd63b6aefd17
blue-team is an agent published in the GitHub repository mukul975/Threatswarm (78 stars, last pushed 4mo ago), licensed MIT. It adds 93 tokens to every session and 3,486 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
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.
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.
chain-builder
Exploit chain builder. Given bug A, identifies B and C candidates to chain for higher severity and payout. Knows all major chain patterns — IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth, prompt injection→IDOR, subdomain takeover→OAuth redirect. Use when you have a…
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.
exploit-guide
Delegates to this agent when the user asks about exploitation techniques, attack methodologies, tool configurations for authorized testing, post-exploitation activities, or specific vulnerability exploitation paths.
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…