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/choiyounggi/groundworkWrote 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/plugins/choiyounggi/groundwork/marketplace)<a href="https://agentmods.dev/plugins/choiyounggi/groundwork/marketplace"><img src="https://agentmods.dev/badge/plugins/choiyounggi/groundwork/marketplace/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/plugins/choiyounggi/groundwork/marketplace"><img src="https://agentmods.dev/badge/plugins/choiyounggi/groundwork/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade C, and why
groundwork marketplace scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"description": "Safe-by-default guardrails for Claude Code — blocks supply-chain / disk-destroying / fork-bomb commands and asks before rm -rf, force-push, DROP/TRUNCATE, kubectl delete, secret/credential access, and clo How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "groundwork",
"description": "A safe-by-default, batteries-included Claude Code harness starter pack — guardrails, a wiki-grounded quality loop, and a memory lifecycle.",
"owner": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"plugins": [
{
"name": "guardrails",
"description": "Safe-by-default guardrails for Claude Code — blocks supply-chain / disk-destroying / fork-bomb commands and asks before rm -rf, force-push, DROP/TRUNCATE, kubectl delete, secret/credential access, and cloud-resource deletion. Every rule configurable. Plus a redacted audit log.",
"category": "development",
"author": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"source": "./plugins/guardrails",
"homepage": "https://github.com/choiyounggi/groundwork",
"version": "1.2.4",
"tags": [
"security",
"guardrails",
"hooks",
"safety",
"agent-safety",
"claude-code"
]
},
{
"name": "memory-loop",
"description": "A memory lifecycle for Claude Code's native memory — a save gate against hallucinated memories, tiered expiry (short-tier memories archived, never deleted), a propose-then-confirm consolidation pass that merges and dedupes long-tier memory, a correction-signal hook that logs likely corrections for the consolidate pass, a two-file habit frame (HABITS.md always loaded, HABITS-CASES.md on demand), and an optional one-time identity setup where the assistant can pick its own name. Local-only.",
"category": "development",
"author": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"source": "./plugins/memory-loop",
"homepage": "https://github.com/choiyounggi/groundwork",
"version": "2.3.1",
"tags": [
"memory",
"habits",
The plugins it lists here
This marketplace lists 2 plugins kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 2d ago Changed 3b246de35270
- 3d ago Changed · +21 lines f5e46165d959
- 6d ago Changed b4a023aad7e5
- 7d ago Changed eef1599b9001
- 8d ago Changed 35020de97e93
- 11d ago Changed 3b843194a687
- 17d ago Changed 98b2abe82e9a
- 19d ago Changed · +25 lines 3abf00ade6a7
- 20d ago Changed 3c9e06c6ffba
- 26d ago First seen · 77 lines scan C 37f73b2fb791
groundwork marketplace is a plugin published in the GitHub repository choiyounggi/groundwork (3 stars, last pushed 3d 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 C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
clean-context
Keeps a project's noise out of Claude's default context: audit-context measures where the budget is going, ignore-setup applies a managed .ignore, a Glob setting, and a short read-deny list for secrets, leaving every excluded path readable on purpose.
compact-nudge
Suggests /compact or /clear when the context grows past a threshold or the prompt cache has gone cold, since every request re-reads the whole context.
esp32-cpp
Evidence-first ESP32 firmware guidance for hardware, FreeRTOS, memory, peripherals, and field failures.
context-police
Measure, trim, and report the token cost of a runaway Claude Code skills/agents catalog (injected every turn + into every subagent) — verified per-project skillOverrides + global disable-model-invocation levers, an interactive HTML recap, and the durable root-cause fix (curate episodic lessons out of the always-on…
memory-hygiene
Audit and clean up Claude Code's persistent memory system — MEMORY.md, memory topic files, lessons, axioms, phase templates, ADRs, and the project docs/ taxonomy.
session-handoff
End-of-session handoff with bucket-aware dispatch across the canonical 7-bucket docs/ taxonomy (aligned with memory-hygiene v3.3), doc-freshness reverse-lint + skill-freshness audit, and future-to-do emission as GitHub issues. Captures knowledge, routes artifacts to…