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.
git 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/agents/open-gsd/gsd-core/gsd-mempalace-curator.compact)<a href="https://agentmods.dev/agents/open-gsd/gsd-core/gsd-mempalace-curator.compact"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-mempalace-curator.compact/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/agents/open-gsd/gsd-core/gsd-mempalace-curator.compact"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-mempalace-curator.compact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00059 | $0.00985 |
| Opus 5.5 | $0.00024 | $0.00394 |
| Sonnet 5.5 | $0.00012 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
gsd-mempalace-curator 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandatory Initial Read: if the prompt has a <required_reading> block, Read every listed file first.
Gate
mempalace.enabled !== true → do nothing, report MemPalace disabled — curation skipped. Check first.
Wing / mode / transport
- Wing:
mempalace.wingif non-empty, elseproject_code, else repo dir name. Every call is scoped to this one wing. - Mode (
mempalace.memory_mode):augment→ KG writes are additive mirror of.planning/graphs/.kg_backend/replace→ palace KG is authoritative — still mirror every fact here as primary target; GSD's normal graphify keeps.planning/graphs/current so an unreachable palace never loses history. - Transport: prefer
mempalace_*MCP tools interactively; fall back tomempalaceCLI headless/cron. Neither reachable → report unavailability and stop, do not error.
Tasks (each independently best-effort)
-
Diary entry (unless
mempalace.diary_journal === false; absent = enabled). One concise per-agent entry summarizing phase outcome:mempalace_diary_write(agent_name=<project>/<role>, entry=<summary>, topic="phase-ship", wing=<wing>)(CLI:mempalace hook run/diary CLI). Namespaceagent_nameby repo+role so diaries don't collide across projects. Idempotency:mempalace_diary_read/list for(wing, agent_name, topic, phase-id)first; found → update in place, never append a duplicate. -
extract-learnings → KG mirror (unless
mempalace.mirror_kg === false; absent = enabled). Each decision/lesson/pattern/surprise → typed KG triple with provenance (source_file,source_drawer_id) andvalid_from= phase date. Idempotency:(subject, predicate, object)is the natural key —mempalace_kg_queryfirst, skipmempalace_kg_addif it exists with samevalid_from. Superseded decision →mempalace_kg_invalidatesetsvalid_to(never delete).
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.
- 1mo ago First seen · 46 lines · 59 tokens per session scan A 1c7a46e57c27
gsd-mempalace-curator is an agent published in the GitHub repository open-gsd/gsd-core (10,622 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 985 once invoked, about $0.0002 per session on Opus 5.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-10.
Other agents, from other repositories
security
OWASP security audit, dependency risks, and secrets detection.
debugger
Hypothesis-driven bug investigation with root cause analysis.
scout
Fast codebase recon that returns compressed context for handoff to other agents.
typescript-pro
TypeScript specialist for advanced type system patterns, complex generics, type-level programming, and end-to-end type safety across full-stack applications. Use when designing type-first APIs, creating branded types for domain modeling, building generic utilities, implementing discriminated unions for state machines…
javascript-pro
Modern JavaScript specialist for browser, Node.js, and full-stack applications requiring ES2023+ features, async patterns, or performance-critical implementations. Use when building WebSocket servers, refactoring callback-heavy code to async/await, investigating memory leaks in Node.js, scaffolding ES module libraries…
git-ops
Conflict resolution, rebase strategy, PR preparation, and changelog generation.