/engage.memory
Cross-engagement pattern memory — recall prior techniques, record confirmed findings, housekeeping
> /plugin marketplace add hypnguyen1209/offensive-claude > /plugin install offensive-claude@offensive-claude-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/engage.memory
Context preview
What this command does when you run it.
Cross-engagement pattern memory — recall prior techniques, record confirmed findings, housekeeping
Command definition
engage.memory.mddescription: Cross-engagement pattern memory — recall prior techniques, record confirmed findings, housekeeping
/engage.memory
Manage the cross-engagement learning store (`skills/engagement-memory`). Patterns are ranked by impact (CVSS/severity) and recalled as an explicit top-N query.
Usage
`/engage.memory <recall|record|gc|stats> [options]`
Subcommands
recall
Pull the top prior patterns for the current target's class / tech stack and write them to `.engage/recon/prior-intel.md` so weaponization starts from what already worked.
python skills/engagement-memory/scripts/pattern_db.py match \
--vuln-class <class> --tech-stack <a,b> --target <host> --top 10 --jsonrecord
Persist a `[CONFIRMED]` finding (run after `/engage.report` / `validate_findings.py`). Only confirmed findings are recorded; `[POSSIBLE]`/`[REJECTED]` are not learned.
python skills/engagement-memory/scripts/pattern_db.py record --json '<finding json>'
gc
Compact the pattern DB (dedup-merge, knowledge preserved) and rotate the disposable audit log.
python skills/engagement-memory/scripts/pattern_db.py compact
stats
Show pattern counts by vulnerability class.
Notes
- Storage: `~/.claude/engagement-memory/patterns.jsonl` (override `$ENGAGEMENT_DB`; use a per-client DB
if ROE requires client isolation).
- Recall is generic-by-class/stack; review before reusing across clients.
- Records hold technique + CWE/CVSS + an evidence *reference*, never raw loot.
Read more
description: Cross-engagement pattern memory — recall prior techniques, record confirmed findings, housekeeping
/engage.memory
Manage the cross-engagement learning store (`skills/engagement-memory`). Patterns are ranked by impact (CVSS/severity) and recalled as an explicit top-N query.
Usage
`/engage.memory <recall|record|gc|stats> [options]`
Subcommands
recall
Pull the top prior patterns for the current target's class / tech stack and write them to `.engage/recon/prior-intel.md` so weaponization starts from what already worked.
python skills/engagement-memory/scripts/pattern_db.py match \
--vuln-class <class> --tech-stack <a,b> --target <host> --top 10 --jsonrecord
Persist a `[CONFIRMED]` finding (run after `/engage.report` / `validate_findings.py`). Only confirmed findings are recorded; `[POSSIBLE]`/`[REJECTED]` are not learned.
python skills/engagement-memory/scripts/pattern_db.py record --json '<finding json>'
gc
Compact the pattern DB (dedup-merge, knowledge preserved) and rotate the disposable audit log.
python skills/engagement-memory/scripts/pattern_db.py compact
stats
Show pattern counts by vulnerability class.
Notes
- Storage: `~/.claude/engagement-memory/patterns.jsonl` (override `$ENGAGEMENT_DB`; use a per-client DB
if ROE requires client isolation).
- Recall is generic-by-class/stack; review before reusing across clients.
- Records hold technique + CWE/CVSS + an evidence *reference*, never raw loot.
A spec-driven offensive security framework for Claude Code — structured engagement workflows based on the Cyber Kill Chain, 31 kill-chain skills (multi-file progressive-disclosure) plus a discipline layer (a SessionStart dispatcher + 6 process/discipline
Repo: hypnguyen1209/offensive-claude
Other commands on offensive-claude.
- /engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement
Open command - /engage.c2
Execute Phase 6 - Command and Control Infrastructure Setup
Open command - /engage.crash
Crash → root cause → reachability → empirical exploitability verdict (native bugs)
Open command - /engage.cvediff
Find the canonical fix commit(s) for a CVE across sources, then diff for root cause
Open command - /engage.deliver
Execute Phase 3 - Delivery and Payload Deployment
Open command - /engage.exploit
Execute Phase 4 - Exploitation and Access Establishment
Open command