AndrewDongminYoo

Cc Agents Kit — Development skill for Claude Code

Development community

Claude Code plugin marketplace.

How to install Cc Agents Kit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open AndrewDongminYoo/cc-agents-kit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Cc Agents Kit does

Claude Code plugin marketplace. guard-hooks: five defensive hooks that block dangerous shell commands and secrets access, catch the two zsh quoting mistakes that fail silently, and warn on lockfile drift and shellcheck findings.

Alternatives in Development

README

cc-agents-kit

[![ci](https://github.com/AndrewDongminYoo/cc-agents-kit/actions/workflows/ci.yml/badge.svg)](https://github.com/AndrewDongminYoo/cc-agents-kit/actions/workflows/ci.yml)

A Claude Code plugin marketplace. Each plugin is scoped to one pain, so you install the part you want and nothing else.

![A search that silently returns the wrong answer, then the same search blocked before it runs](docs/guard-hooks.gif)

/plugin marketplace add AndrewDongminYoo/cc-agents-kit
/plugin install guard-hooks@cc-agents-kit

Upgrading needs `claude plugin update guard-hooks@cc-agents-kit` — the marketplace suffix is required, and installing again is a no-op that reports success. Refreshing the marketplace alone is not enough: the cache keeps one directory per version, and the runtime loads the version recorded at install time, so `claude plugin details` can report the new version while the old one is still what fires. Hooks are read when a session starts, so restart any session that is already open.

Plugin What it does
`guard-hooks` Seven defensive hooks — five block, two warn.
`context-handoff` Carry work across sessions, and keep the context that carries it lean.
`repo-gate` What runs between "the code works" and "it is pushed".

guard-hooks

Why the zsh quoting guard exists

Two shell mistakes recur across agent sessions, and both fail *silently* rather than with an error you would notice.

**A backtick inside a double-quoted commit or PR message.** zsh runs it as command substitution, so the backticked word is deleted from the message before git ever sees it — and the `command not found` scrolls past in the commit output.

git commit -m "fix: cancel `players` subscription"
# committed message: "fix: cancel  subscription"   ← the word is gone

**An unquoted glob in an option value.** zsh expands it against the current directory before the tool is eve