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/guardrails)<a href="https://agentmods.dev/plugins/choiyounggi/groundwork/guardrails"><img src="https://agentmods.dev/badge/plugins/choiyounggi/groundwork/guardrails/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/guardrails"><img src="https://agentmods.dev/badge/plugins/choiyounggi/groundwork/guardrails.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade C, and why
guardrails 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 6d 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: a PreToolUse Bash guard that blocks supply-chain / disk-destroying / fork-bomb commands and asks before rm -rf, force-push, DROP/TRUNCATE, kubectl delete, secre What it actually says
{
"name": "guardrails",
"displayName": "guardrails",
"description": "Safe-by-default guardrails for Claude Code: a PreToolUse Bash guard that 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 (off / ask / block) — plus a redacted PostToolUse audit log. No org-specific rules; generic across any project.",
"version": "1.2.4",
"author": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"homepage": "https://github.com/choiyounggi/groundwork",
"license": "MIT",
"repository": "https://github.com/choiyounggi/groundwork",
"icon": "./assets/icon.png",
"keywords": ["security", "safety", "guardrails", "hooks", "pretooluse", "destructive-commands", "audit-log", "yolo-mode"]
}
What it installs
The manifest is a name and a version. 1 skill, 2 hooks travel with it, and installing the plugin installs all of them — 79 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 6d ago Changed 66939e2da16f
- 7d ago Changed · +5 lines 34cf20ee9fd4
- 1mo ago Changed 46851aba1676
- 1mo ago First seen · 11 lines scan C e49da4437d11
guardrails 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
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…
systems-architecture
Systems architecture and distributed systems skills including Designing Data-Intensive Applications (Martin Kleppmann), System Design Interview (Alex Xu), Clean Architecture (Robert C. Martin), Release It! (Michael Nygard), High Performance Browser Networking (Ilya Grigorik), and Team Topologies (Skelton & Pais).
product-strategy
Product strategy and innovation frameworks including Jobs to Be Done (Clayton Christensen) for customer discovery and product design, tactical negotiation skills (Chris Voss), willingness-to-pay pricing (Monetizing Innovation), and startup metrics (Lean Analytics).
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
handbook-dotnet
.NET development skills: running single C# files, testing, coverage, API inspection, analyzers and Roslyn queries.
handbook-discover
Discover and audit all plugins in a Claude Code marketplace with installation status, versions, and component breakdown.