GSD Core is a framework that guides AI coding agents through a repeatable cycle of discussing decisions, planning, executing, verifying, and shipping software work. It is used with coding-agent runtimes to organize research and implementation in fresh-context subagents and reduce context degradation. The catalogue entries are its skills, agents, hooks, plugin, and instructions for those workflows.
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.
npx skills add open-gsd/gsd-core --skill gsd-mempalace-recallgit clone --depth 1 https://github.com/open-gsd/gsd-coreWrote 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/skills/open-gsd/gsd-core/gsd-mempalace-recall)<a href="https://agentmods.dev/skills/open-gsd/gsd-core/gsd-mempalace-recall"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-core/gsd-mempalace-recall/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/skills/open-gsd/gsd-core/gsd-mempalace-recall"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-core/gsd-mempalace-recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.01438 |
| Opus 5 | $0.00011 | $0.00719 |
| Sonnet 5 | $0.00004 | $0.00288 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
gsd-mempalace-recall 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ferrox-mempalace-recall — 91% identical, 19 lines differ
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by the command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.
Step 0 -- Banner
Before ANY tool calls, display this banner:
GSD > MEMPALACE RECALL
Then proceed to Step 1.
Step 1 -- Config Gate
Check whether the MemPalace capability is enabled by reading .planning/config.json directly with the Read tool.
DO NOT use gsd-tools config get-value -- it hard-exits on missing keys.
- Read
.planning/config.jsonwith the Read tool. - If the file does not exist: write the "unavailable" stub (Step 4) and STOP.
- Parse the JSON. Proceed to Step 2 only if
config.mempalace && config.mempalace.enabled === trueandconfig.mempalace.recall_on_plan !== false. Otherwise display the disabled message and STOP (recall_on_plan: falseturns plan-time recall off while leaving the rest of the capability enabled).
Disabled message:
GSD > MEMPALACE RECALL
MemPalace memory is disabled. To activate:
node <runtime-home>/gsd-core/bin/gsd-tools.cjs config-set mempalace.enabled true
Recall is opt-in; the loop proceeds normally without it.
This step is onError: skip at plan:pre -- recall never blocks planning.
Step 2 -- Resolve wing, mode, and transport
- Wing. Use
config.mempalace.wingif non-empty; otherwise derive fromconfig.project_code; otherwise fall back to the repository directory name. - Mode. Read
config.mempalace.memory_mode(augment|kg_backend|replace, defaultaugment). It sets how authoritative the palace is during recall:augment— the palace is an additional layer; read native memory (.planning/graphs/, STATE) too and treat the palace as supplementary.kg_backend— for knowledge-graph facts, query the palace's temporal KG first, as the primary source; fall back to.planning/graphs/when the palace is unreachable. Non-KG drawer recall stays additive.replace— resolve recall through the palace as the source of truth; consult native artifacts only as a fallback when the palace is unreachable. In every mode an unreachable palace degrades to native memory — recall never blocks (onError: skip).
- Transport. Prefer the MCP tools (
mempalace_*) in interactive runs when your MemPalace MCP server is registered and your runtime permits those tools. Otherwise — headless/cron/autonomous runs, or runtimes that don't grant the MemPalace MCP tools — use the CLI (mempalace wake-up,mempalace search), which this skill'sBashallow-tool always covers. If neither is reachable, go to Step 4. - Topic. Read the phase
CONTEXT.md(the consumed artifact). Derive a short search query from its title, goal, and key decisions.
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.
- 4d ago Changed · +1 lines b756396ab440
- 7d ago First seen · 107 lines · 22 tokens per session scan A a47ec5d5d7e5
gsd-mempalace-recall is a skill published in the GitHub repository open-gsd/gsd-core (9,319 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,438 once invoked, about $0.0001 per session on Opus 5. 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-09-03.
Other skills, from other repositories
handoff
Prepare a clean cross-session handoff so the next agent can pick up where you left off. Writes a focused continue.md in the active slice dir and ensures STATE.md + summary artifacts are current. Use when asked to "hand off", "prepare handoff", "pause work", "bookmark this", "I'll come back to this later", before…
director:resume
Pick up where you left off after a break. Restores your context automatically.
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
gsd-orchestrator
Build software products autonomously via GSD headless mode. Handles the full lifecycle: write a spec, launch a build, poll for completion, handle blockers, track costs, and verify the result. Use when asked to "build something", "create a project", "run gsd", "check build status", or any task that requires autonomous…
gsd-headless
Orchestrate GSD (Git Ship Done) projects programmatically via headless CLI. Use when an agent needs to create milestones from specs, execute dev workflows, monitor progress, check status, or control execution (pause/stop/skip/steer). Triggers on "run gsd", "create milestone", "execute project", "check gsd status"…