memory

Stores and retrieves security context memories for incident analysis.

Updated May 7, 2026

Search Tags:#memory #audit-trail #security-context #incident-analysis #history-search #context-recall

Ready to run

npx skills add https://github.com/gongzeq/VAPT3 --skill memory-gongzeq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/gongzeq/VAPT3/tree/main/secbot/skills/memory
Command: npx skills add https://github.com/gongzeq/VAPT3 --skill memory-gongzeq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory of security context and historical findings is often lost across sessions, hindering incident analysis and ongoing investigations.

Core Features & Use Cases

Long-term security context storage (targets, findings, operational notes) and fast historical search using built-in grep-like tooling.
Append-only memory store for reproducible investigations and auditable trails.

Quick Start

Search past security events with memory to locate prior findings and notes.

Frequently Asked Questions about memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I retain security context and past findings across multiple investigation sessions?▼

You can retain security context by using an append-only memory store that saves targets, findings, and operational notes, enabling quick recall and historical search across long-running investigations and cross-session tasks.

What is the best way to search past security events for incident analysis?▼

The best way to search past security events is using built-in grep-like tooling within the memory store, allowing fast historical search to locate prior findings and operational notes during incident analysis.

How does an append-only audit trail support reproducible security investigations?▼

An append-only audit trail supports reproducible security investigations by preventing modification of stored context memories, ensuring targets and findings remain intact for reliable historical review and compliance.

Can I integrate recalled security context directly with my investigation orchestrator?▼

Yes, recalled security context integrates seamlessly with the Orchestrator, allowing you to inject past targets and findings directly into active workflows without manual context reconstruction.

Does this memory store work for long-running audits requiring operational notes?▼

Yes, this memory store works for long-running audits by providing durable storage for operational notes and findings, supporting quick recall and context retrieval throughout extended audit timelines.

When do I need a dedicated history store for incident analysis?▼

You need a dedicated history store for incident analysis when investigations span multiple sessions and require fast search capabilities to recall targets, findings, and operational notes without losing context.