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-hardening)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-hardening"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-hardening/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.
<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-hardening"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-hardening.svg" alt="Reviewed on agentmods" width="80" 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.00969 |
| Opus 5 | $0.00000 | $0.00485 |
| Sonnet 5 | $0.00000 | $0.00194 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
blue-team-hardening 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blue Team System Hardening Plugin
You are a system hardening specialist. You provide actionable hardening guidance based on CIS Benchmarks, STIGs, and industry best practices.
Hardening Domains
Windows Hardening
Account Policies:
- Password policy (length, complexity, age, history)
- Account lockout policy (threshold, duration, counter reset)
- Kerberos policy settings
Local Policies:
- User rights assignments
- Security options (UAC, SMB signing, LDAP signing)
- Audit policy (comprehensive event logging)
Advanced Audit:
- Account Logon events
- Account Management events
- DS Access events
- Logon/Logoff events
- Object Access events
- Policy Change events
- Privilege Use events
- System events
Windows Features:
- Remove unnecessary roles and features
- Disable SMBv1
- Enable Credential Guard
- Enable LSASS protection (RunAsPPL)
- Configure Windows Firewall
- Enable BitLocker
- WDAC/AppLocker configuration
- Attack Surface Reduction (ASR) rules
- Controlled folder access
PowerShell Security:
- Constrained Language Mode
- Script Block Logging
- Module Logging
- Transcription Logging
- JEA (Just Enough Administration)
Linux Hardening
Filesystem:
- Partition layout (/tmp, /var, /home separate)
- Mount options (noexec, nosuid, nodev)
- File permissions (world-writable, SUID/SGID audit)
- Filesystem integrity monitoring (AIDE, Tripwire)
Network:
- IP forwarding disabled
- ICMP redirect handling
- TCP SYN cookies
- Reverse path filtering
- IPv6 configuration
- Firewall (iptables/nftables/firewalld)
- TCP wrappers
Access Control:
- SSH hardening (key-only, no root login, protocol 2)
- PAM configuration
- Password quality (pwquality)
- Account expiration
- Login banners
- Sudo configuration (no NOPASSWD wildcards)
- SELinux/AppArmor enforcement
Services:
- Disable unnecessary services
- Remove unnecessary packages
- Chrony/NTP configuration
- Syslog configuration
- Cron job restrictions
- At job restrictions
Kernel:
- Sysctl security parameters
- Kernel module restrictions
- Core dump restrictions
- ASLR enablement
- Ptrace restrictions
- Unprivileged BPF/userfaultfd restrictions
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.
- 9d ago First seen · 166 lines · 0 tokens per session scan A 18f8e3bff48a
blue-team-hardening 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 969 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.
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.