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.
/plugin marketplace add choiyounggi/groundworknpx agentmods add plugins/choiyounggi/groundwork/memory-loopgit clone --depth 1 https://github.com/choiyounggi/groundworkGrade A, and why
memory-loop 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 yesterday.
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.
What it actually says
{
"name": "memory-loop",
"description": "A memory lifecycle for Claude Code's native file-based memory: a save gate against hallucinated memories, tiered expiry (short-tier memories archived — never deleted — when they lapse), a propose-then-confirm consolidation pass (merge/dedupe long-tier memory), a periodic learning-review nudge, a two-file habit frame (rules always loaded, case records on demand), and an optional identity setup (names for the user and the assistant). Local-only, English, no org-specific content.",
"version": "1.5.0",
"author": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"homepage": "https://github.com/choiyounggi/groundwork"
}
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.
- yesterday First seen · 11 lines scan A e0788cc0a79c
memory-loop is a plugin published in the GitHub repository choiyounggi/groundwork (3 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
learnable
Learn any subject properly, in courses you actually finish. Four commands: learn is the way in and the way back, new-course researches a whole domain with a fleet of agents and turns it into a taxonomy and a plan aimed at your real gaps, self-assess measures your true level with a scenario quiz that cannot be gamed…
open-design-guide
Teaches Claude to use the Open Design content library: 151 design systems with real tokens, 71 design and frontend skills, 114 rendering templates. Installs the library as a sparse clone, no desktop app and no daemon.
rtl-chat-fixer
Fixes jumbled RTL text in Cowork/Claude Desktop chat by teaching Claude how to structure mixed-direction responses for Hebrew, Arabic, Persian, Urdu and other RTL languages.
agents-md-optimizer
Audit bloated agent-instruction files (CLAUDE.md, AGENTS.md, and their variants) and rewrite them lean, or author a new one from scratch following the 200-line recipe-book principle. Detects anti-patterns like embedded API docs, negative rules, tutorials, and preemptive file preloads.
quiz-me
Skills that keep you in the loop on your own codebase.
quiz-me
Gates code changes behind an interactive quiz: Claude investigates, tests your understanding of root cause and fix, and only implements once you pass.