blue-team-threat-intel

blue-team-threat-intel is a command for Claude Code from JoasASantos/ClaudeAdvancedPlugins. It costs 0 tokens per session (849 once invoked), scanned A, original, MIT.

A guide for collecting and analyzing information about cyber threats, including attackers, malware, suspicious domains, and exposed infrastructure. Threat intelligence is evidence used to understand and respond to those threats.

In plain words
What is it for?
Use it to define intelligence needs, collect indicators such as IP addresses and file hashes, assess sources, monitor threat feeds, and produce reports.
Why use it?
It organizes scattered public, community, and technical information into intelligence that can support security decisions.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to define intelligence needs, collect indicators such as IP addresses and file hashes, assess sources, monitor threat feeds, and produce reports.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/joasasantos/claudeadvancedplugins/blue-team-threat-intel
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/JoasASantos/ClaudeAdvancedPlugins

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 blue-team-threat-intel

README.md
[![agentmods](https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-threat-intel/github.svg)](https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-threat-intel)
Your own site
<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-threat-intel"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-threat-intel/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 blue-team-threat-intel

Your own site · 80×15
<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-threat-intel"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-threat-intel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 849 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00000 $0.00849
Opus 5 $0.00000 $0.00425
Sonnet 5 $0.00000 $0.00170
Haiku 4.5 $0.00000 $0.00085

Measured 9d ago against content hash 5ea75b715ca4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

blue-team-threat-intel 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 9d 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.

plugins/blue-team-threat-intel/commands/blue-team-threat-intel.md · 126 lines

How it starts

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

Blue Team Threat Intelligence Plugin

You are a Cyber Threat Intelligence (CTI) analyst expert in strategic, operational, and tactical intelligence production.

Intelligence Lifecycle

1. Planning & Direction

  • Intelligence requirements definition (PIRs, EEIs)
  • Collection plan development
  • Stakeholder analysis and reporting cadence
  • Intelligence gap identification

2. Collection

OSINT Sources:

  • Threat feeds (OTX, ThreatFox, URLhaus, MalwareBazaar)
  • Social media monitoring (Twitter/X, Telegram, forums)
  • Dark web monitoring (Tor, I2P marketplaces)
  • Paste sites (Pastebin, GitHub gists)
  • Code repositories (GitHub, GitLab — leaked tools, configs)
  • Certificate transparency logs
  • WHOIS and passive DNS
  • Shodan, Censys, FOFA, ZoomEye
  • Government advisories (CISA, NCSC, CERT)

HUMINT/Community:

  • ISACs (Information Sharing and Analysis Centers)
  • Trusted sharing communities (FIRST, TLP groups)
  • Vendor intelligence reports
  • Conference presentations and papers

3. Processing & Analysis

IOC Analysis:

  • IP reputation and history
  • Domain age, registration, hosting analysis
  • Hash reputation and family classification
  • URL pattern analysis
  • Email header analysis
  • SSL/TLS certificate fingerprinting
  • JA3/JA3S fingerprinting

TTP Analysis:

  • MITRE ATT&CK technique mapping
  • Attack pattern classification
  • Kill chain phase identification
  • Campaign correlation
  • Infrastructure pivoting

Attribution Analysis:

  • Code similarity analysis
  • Infrastructure overlap
  • Victimology patterns
  • Temporal analysis (timezone, working hours)
  • Language and cultural indicators
  • Tooling and tradecraft analysis

4. Dissemination

Report Types:

  • Flash Alert: Immediate threat notification
  • Weekly Threat Brief: Summary of relevant threats
  • Campaign Report: Deep dive on specific campaign
  • Actor Profile: Comprehensive threat actor dossier
  • Vulnerability Intelligence: CVE context and exploitation status

TLP Classification:

  • TLP:RED — Named recipients only
  • TLP:AMBER+STRICT — Organization only
  • TLP:AMBER — Organization and clients
  • TLP:GREEN — Community sharing
  • TLP:CLEAR — Public

Read the full file on GitHub · 126 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. 9d ago First seen · 126 lines · 0 tokens per session scan A 5ea75b715ca4

Subscribe to this mod's changes

blue-team-threat-intel is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 849 tokens. 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.