Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Security framework for AI agents. Enforces instruction gateway control, external action gating, PII protection, sub-agent sandboxing, prompt injection detect...
Security framework for AI agents. Enforces instruction gateway control, external action gating, PII protection, sub-agent sandboxing, prompt injection detect...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Give your agent a brain that persists between sessions and protect it from memory poisoning attacks.
This skill documents a local memory/security tool. It does not auto-install packages or silently execute shell commands. Any install command shown here is a manual setup step for the user to approve and run explicitly. Local ShieldCortex usage does not require credentials. API keys are optional and only needed for ShieldCortex Cloud. Only scan instruction files or other prompts when the user has named the path or clearly asked for that review. shieldcortex install writes local MCP configuration; it does not deploy a remote service or request background privileges.
You want to remember things between sessions (decisions, preferences, architecture, context) You need to recall relevant past context at the start of a session You want knowledge graph extraction from memories (entities, relationships) You need to protect memory from prompt injection or poisoning attacks You want credential leak detection in memory writes You want to audit what has been stored in and retrieved from memory You want to scan instruction files (SKILL.md, .cursorrules, CLAUDE.md) for threats
Install the npm package globally, then configure the MCP server, only when the user explicitly wants ShieldCortex enabled: npm install -g shieldcortex shieldcortex install Python SDK also available: pip install shieldcortex
At the start of every session, retrieve prior context: Call start_session to begin a new session and get relevant memories Or call get_context with a query describing the current task
Call remember immediately when any of these happen: Architecture decisions โ "We're using PostgreSQL for the database" Bug fixes โ capture root cause and solution User preferences โ "Always use TypeScript strict mode" Completed features โ what was built and why Error resolutions โ what broke and how it was fixed Project context โ tech stack, key patterns, file structure Parameters: title (required): Short summary content (required): Detailed information category: architecture, pattern, preference, error, context, learning, todo, note importance: low, normal, high, critical project: Scope to a specific project (auto-detected if omitted) tags: Array of tags for categorisation
Call recall to search for past memories: mode: "search" โ query-based semantic search (default) mode: "recent" โ most recent memories mode: "important" โ highest-salience memories Filter by category, tags, project, or type (short_term, long_term, episodic).
Call forget to remove outdated or incorrect memories: Delete by id for a specific memory Delete by query to match content Always use dryRun: true first to preview what will be deleted Use confirm: true for bulk deletions
Call end_session with a summary to trigger memory consolidation. This promotes short-term memories to long-term and runs decay on old, unaccessed memories.
ShieldCortex automatically extracts entities and relationships from memories. graph_query โ traverse from an entity, returns connected entities up to N hops graph_entities โ list known entities, filter by type (person, tool, concept, file, language, service, pattern) graph_explain โ find the path connecting two entities Use the knowledge graph to understand relationships between concepts, technologies, and decisions across the project.
consolidate โ merge duplicate/similar memories, run decay. Use dryRun: true to preview detect_contradictions โ find conflicting memories (e.g., "use Redis" vs "don't use Redis") get_related โ find memories connected to a specific memory ID link_memories โ create explicit relationships (references, extends, contradicts, related) memory_stats โ view total counts, category breakdown, decay stats
Every memory write passes through a 6-layer defence pipeline: Input Sanitisation โ strips control characters and null bytes Pattern Detection โ regex matching for known injection patterns Semantic Analysis โ embedding similarity to attack corpus Structural Validation โ JSON/format integrity checks Behavioural Scoring โ anomaly detection over time Credential Leak Detection โ blocks API keys, tokens, private keys (25+ patterns, 11 providers)
Behavioural security layer that controls what agents can do, not just what they remember: iron_dome_activate โ activate with a profile: school, enterprise, personal, or paranoid iron_dome_status โ check active profile, trusted channels, and approval rules iron_dome_check โ gate an action (e.g., send_email, delete_file) before execution iron_dome_scan โ scan text for prompt injection patterns Profiles control action gates (what actions require approval), channel trust (which instruction sources are trusted), and approval rules.
audit_query โ query the forensic audit log of all memory operations defence_stats โ view defence system statistics (blocks, allows, quarantines) quarantine_review โ review and manage quarantined memories (list, approve, reject) scan_memories โ scan existing memories for signs of poisoning scan_skill โ scan an instruction file for hidden threats (SKILL.md, .cursorrules, CLAUDE.md, etc.)
ShieldCortex can act as a security layer for any memory backend โ not just its own. Use ShieldCortexGuardedMemoryBridge to wrap any memory system with the full defence pipeline: import { ShieldCortexGuardedMemoryBridge, MarkdownMemoryBackend } from 'shieldcortex'; const bridge = new ShieldCortexGuardedMemoryBridge({ backend: new MarkdownMemoryBackend('~/.my-memories/'), }); // All writes pass through the 6-layer defence pipeline await bridge.write({ title: 'Decision', content: 'Use PostgreSQL' }); Built-in backends: MarkdownMemoryBackend, OpenClawMarkdownBackend. Implement the backend interface for custom storage. ShieldCortex does not auto-discover remote backends or obtain their credentials; the host application must wire that in explicitly.
set_project โ switch active project context get_project โ show current project scope Use project: "*" for global/cross-project memories
Remember immediately โ call remember right after a decision is made or a bug is fixed, not at the end of the session Use categories โ architecture, pattern, preference, error, context, learning Set importance โ mark critical decisions as importance: "critical" so they resist decay Recall at session start โ always call get_context or start_session first End sessions properly โ call end_session with a summary to trigger consolidation Review contradictions โ periodically run detect_contradictions to catch conflicting information Scope by project โ memories are automatically scoped to the current project directory
Memory not found in recall: Try mode: "search" with different query phrasing Check set_project โ you may be searching the wrong project scope Use includeDecayed: true to find memories that have faded Memory blocked by firewall: The defence pipeline detected a potential threat (injection, credential leak) Check audit_query for the specific block reason Review with quarantine_review if it was a false positive Avoid including literal API keys or tokens in memory content Consolidation removing memories: Run consolidate with dryRun: true first to preview Mark important memories as importance: "critical" to prevent decay Access memories regularly โ recall boosts activation and prevents decay
When using the OpenClaw hook, auto-memory extraction is off by default. Enable it to automatically extract memories from session output: shieldcortex config --openclaw-auto-memory When enabled, the system deduplicates against recent memories to avoid storing duplicates. Configure with: openclawAutoMemory โ enable/disable (default: false) openclawAutoMemoryDedupe โ deduplicate against existing memories (default: true) openclawAutoMemoryNoveltyThreshold โ similarity threshold for deduplication (default: 0.88) openclawAutoMemoryMaxRecent โ number of recent memories to check (default: 300)
npm: https://www.npmjs.com/package/shieldcortex PyPI: https://pypi.org/project/shieldcortex GitHub: https://github.com/Drakon-Systems-Ltd/ShieldCortex Website: https://shieldcortex.ai
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.