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)<a href="https://agentmods.dev/agents/open-gsd/gsd-core/gsd-mempalace-curator"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-mempalace-curator/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"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-mempalace-curator.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.01160 |
| Opus 5 | $0.00030 | $0.00580 |
| Sonnet 5 | $0.00012 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
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 10d 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
2 near-identical copies found in the catalogue:
- ferrox-mempalace-curator — 88% identical, 12 lines differ
- gsd-mempalace-curator — 88% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL: Mandatory Initial Read
If the prompt contains a <required_reading> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Gate
If mempalace.enabled !== true, do nothing and report MemPalace disabled — curation skipped. This is the hard gate; respect it before any other work.
Wing / mode / transport
- Wing:
mempalace.wingif non-empty, elseproject_code, else the repo directory name. Every call you make is scoped to this one wing. - Mode (
mempalace.memory_mode): underaugment, KG writes are an additive mirror of.planning/graphs/. Underkg_backend/replace, the palace KG is the authoritative fact store — still mirror every fact here as the primary target; GSD's normal graphify keeps.planning/graphs/current, so an unreachable palace never loses history. - Transport: prefer the
mempalace_*MCP tools interactively; fall back to themempalaceCLI in headless/cron runs. If neither is reachable, report unavailability and stop — do not error.
Tasks (each independently best-effort)
- Diary entry (unless
mempalace.diary_journal !== false— registry default is true, an absent key means enabled). Write one concise per-agent diary entry summarising the phase outcome:mempalace_diary_write(agent_name=<project>/<role>, entry=<summary>, topic="phase-ship", wing=<wing>)(CLI:mempalace hook run/ the diary CLI). Namespaceagent_nameby repo+role so diaries don't collide across projects. Idempotency: before writing,mempalace_diary_read(or list) for an existing entry keyed by(wing, agent_name, topic, phase-id); if one exists for this phase, update it in place rather than appending a second.
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.
- 10d ago First seen · 50 lines · 59 tokens per session scan A 38bcde1a5007
gsd-mempalace-curator is an agent published in the GitHub repository open-gsd/gsd-core (9,278 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,160 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
security
OWASP security audit, dependency risks, and secrets detection.
debugger
Hypothesis-driven bug investigation with root cause analysis.
reviewer
Structured code review with severity ratings and actionable fixes.
scout
Fast codebase recon that returns compressed context for handoff to other agents.
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…
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…