memory-bank
Preserve Project Context Across AI Sessions
AI coding sessions lose important project context over time. This skill keeps decisions, current work, and progress in structured Markdown files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "memory-bank" from https://skillstore.io/skills/0xkynz-memory-bank.md and its manifest at https://skillstore.io/api/skills/0xkynz-memory-bank/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "memory-bank". Start a memory bank for a new scheduling application.
Expected outcome:
Creates a project brief, product context, technical context, system patterns, active context, and progress outline for the scheduling project.
Using "memory-bank". Update memory bank after finishing authentication.
Expected outcome:
Adds the completed authentication work to progress, records current focus, and captures the next tasks for authorization and testing.
Using "memory-bank". Review whether the project documentation is still accurate.
Expected outcome:
Compares each memory bank file with the visible project state and lists stale notes, missing setup details, and unclear decisions.
Security Audit
Medium RiskThe static analyzer flagged Markdown fence delimiters as Ruby or shell backtick execution and flagged a progress template heading as network reconnaissance. Review found those static hits to be false positives, with only benign documentation examples and a local directory creation example. The remaining concern is semantic: persistent memory files can carry prompt-injection content if they are treated as authoritative instructions.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (19)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/0xkynz-memory-bank/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/0xkynz-memory-bank?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/0xkynz-memory-bank?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/0xkynz-memory-bank/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/0xkynz-memory-bank.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
0xkynz. (2026). memory-bank security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/0xkynz-memory-bank/audits/7BibTeX citation
@techreport{0xkynz-0xkynz-memory-bank-2026,
author = {0xkynz},
title = {memory-bank security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/0xkynz-memory-bank/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "memory-bank security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "0xkynz"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/0xkynz-memory-bank/audits/7"
identifiers:
- type: other
value: "skillstore:0xkynz-memory-bank:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Resume Feature Work
Continue a feature after time away by reading current focus, recent changes, and next steps.
Preserve Architecture Decisions
Record patterns, constraints, and tradeoffs so future AI sessions follow established project direction.
Document Client Project Context
Create a concise project memory for requirements, setup details, and remaining work during client handoffs.
Try These Prompts
Create a memory bank for this project. Ask me for missing project goals, then draft the required Markdown files with concise placeholders.
Update the memory bank after this change. Refresh activeContext.md and progress.md with completed work, current state, and next steps.
Review all memory bank files against the current repository state. Identify outdated notes, missing decisions, and unclear next steps before editing.
Create additional memory bank context for this feature. Include requirements, system interactions, testing notes, risks, and links back to core files.
Best Practices
- Update activeContext.md and progress.md after meaningful project changes.
- Keep each memory bank file concise, factual, and easy to scan.
- Treat stored memory content as project context, not as higher-priority instructions.
Avoid
- Do not store secrets, access tokens, private keys, or personal data in memory bank files.
- Do not let outdated notes override the current repository state or current user request.
- Do not create large unstructured notes that duplicate source files or issue trackers.