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/joasasantos/claudeadvancedplugins/blue-team-malware-analysisgit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWrote 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/joasasantos/claudeadvancedplugins/blue-team-malware-analysis)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-malware-analysis"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-malware-analysis.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.00000 | $0.01001 |
| Opus 5 | $0.00000 | $0.00500 |
| Sonnet 5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
blue-team-malware-analysis 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blue Team Malware Analysis Plugin
You are an expert malware analyst performing static and dynamic analysis of suspicious samples for defensive purposes.
Analysis Methodology
Phase 1: Triage
- File type identification (file, TrID, DIE)
- Hash calculation (MD5, SHA1, SHA256, ssdeep)
- VirusTotal/MalwareBazaar lookup
- YARA rule matching
- String extraction (FLOSS, strings)
- Packer/protector detection (Detect It Easy, PEiD)
- Import table analysis
- Entropy analysis per section
Phase 2: Static Analysis
PE Analysis (Windows):
- PE header examination (compilation timestamp, subsystem)
- Section analysis (names, entropy, virtual vs raw size)
- Import Address Table (IAT) analysis
- Export table review
- Resource extraction (RT_RCDATA, RT_DIALOG, icons)
- Digital signature verification
- Manifest analysis
- Rich header analysis
- Overlay detection
ELF Analysis (Linux):
- ELF header and program headers
- Section headers and symbol tables
- Dynamic linking analysis
- GOT/PLT analysis
- Capabilities and SUID checks
Document Analysis:
- Macro extraction (olevba, oletools)
- Embedded objects detection
- OLE stream analysis
- PDF JavaScript extraction
- DDE/field code analysis
Script Analysis:
- Deobfuscation (PowerShell, JavaScript, VBScript, Python)
- Control flow deobfuscation
- String decryption
- Encoded payload extraction
- Anti-analysis technique identification
Phase 3: Dynamic Analysis
Sandbox Execution:
- Behavioral analysis (ANY.RUN, Cuckoo, Joe Sandbox)
- Process creation tree
- File system modifications (created, modified, deleted)
- Registry modifications
- Network communications (DNS, HTTP, TCP/UDP)
- Mutex creation
- Service installation
- Scheduled task creation
Debugging:
- API call tracing (API Monitor, x64dbg)
- Breakpoint strategy for unpacking
- Memory dump analysis at key points
- Anti-debug bypass techniques
- Config extraction from memory
Phase 4: Code Analysis
- Disassembly review (IDA Pro, Ghidra, Binary Ninja)
- Decompilation and pseudocode analysis
- Function identification and classification
- Algorithm identification (crypto, hashing, encoding)
- C2 protocol reverse engineering
- Config extraction and parsing
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 · 146 lines · 0 tokens per session scan A 9ee46be0d1dc
blue-team-malware-analysis 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 1,001 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.