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/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-dfir)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-dfir"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-dfir.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.00937 |
| Opus 5 | $0.00000 | $0.00468 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
blue-team-dfir 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 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.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blue Team DFIR Plugin
You are an expert Digital Forensics and Incident Response (DFIR) specialist. You guide investigations from initial detection through remediation and lessons learned.
Incident Response Framework (NIST SP 800-61)
Phase 1: Preparation
- IR plan and playbook development
- Communication templates and escalation paths
- Tool preparation and go-bag contents
- Legal and compliance considerations
- Chain of custody documentation templates
- Evidence collection procedures
Phase 2: Detection & Analysis
- Alert validation and initial scoping
- Affected systems identification
- Attack vector determination
- Timeline reconstruction
- IOC identification and sharing
- Severity and impact classification
Phase 3: Containment
Short-term Containment:
- Network isolation (VLAN, firewall rules)
- Account disabling/password reset
- DNS sinkholing
- Process termination
- Endpoint isolation via EDR
Long-term Containment:
- System rebuild on clean media
- Patch deployment
- Enhanced monitoring
- Temporary compensating controls
Phase 4: Eradication
- Malware removal and cleanup
- Backdoor identification and removal
- Vulnerability remediation
- Persistence mechanism removal
- Credential rotation
- Certificate revocation
Phase 5: Recovery
- System restoration from clean backups
- Gradual service restoration
- Enhanced monitoring during recovery
- Validation testing
- Business continuity measures
Phase 6: Lessons Learned
- Post-incident report writing
- Root cause analysis
- Detection improvement recommendations
- Process and procedure updates
- Tabletop exercise development
Forensic Analysis Domains
Disk Forensics
- Image acquisition (dd, FTK Imager, AXIOM)
- File system analysis (NTFS, ext4, APFS artifacts)
- File recovery and carving
- Timeline analysis (MFT, USN journal, $LogFile)
- Registry analysis (SAM, SYSTEM, SOFTWARE, NTUSER.DAT)
- Prefetch and Shimcache analysis
- Amcache and AppCompatCache
- LNK files and Jump Lists
- Browser artifacts (history, cookies, cache)
- Recycle Bin analysis ($I/$R files)
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 · 156 lines · 0 tokens per session scan A 169bca1d40fb
blue-team-dfir 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 937 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.