8 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceAnswer questions about past agent runs from the recording, not from memory. Three read-only stdlib scripts over the session transcripts Claude Code and Codex already write: a finder that locates the run by repo, time window, touched file or command text; a timeline that numbers every step with its exit code, lists every file changed (flagging changes the agent never mentioned) and walks back from any step with each causal edge labelled recorded or inferred by a named rule; and a claim checker that tests a summary's claims (ran, passed, edited, not-edited, read) against the run and catches tests that passed before a later edit and exit codes that belong to the last command of a pipe. Secrets are always redacted. A UserPromptSubmit hook gives the agent this session's transcript path when a prompt asks about past work. Ships cs-run-forensics agent, /cs-run-forensics and /cs-check-claims commands and 3 cited references.
Turn a tangled working tree into a clean, reviewable commit series. Three deterministic stdlib scripts over git: a series planner that groups changes into commits in build-safe order (manifest with lockfile, pure moves, formatting, each module's change with its tests, docs, CI), holds back .env and key files, and flags mixed formatting and moves whose callers would break; a secret gate that scans staged or pushed lines for provider tokens, high-entropy secrets, sensitive files and conflict markers and blocks before the commit exists, with redacted output and reasoned waivers; and a message linter that blocks vague subjects, missing why on large changes and pending fixup commits, matching the repo's own convention. Ships pre-commit, commit-msg and pre-push hooks, cs-commit-craft agent, /cs-commit-craft and /cs-commit-check commands and 3 cited references.
Roll Claude Code out to a team with guardrails you can check. Four deterministic stdlib scripts: a settings linter that reads shared, local, user and managed settings together (array merge, deny-ask-allow order) and blocks blanket shell allows, pre-approved destructive commands and committed credentials; an MCP and plugin inventory that blocks anything missing from your approved list or holding a literal secret, and flags unpinned or plain-http servers; a CLAUDE.md layering audit that resolves every layer and @import and flags broken imports, contradictions, secrets and resident size; and a privacy-safe adoption tracker that turns local session files into counts only and classifies the rollout as PILOT, SPREADING, EMBEDDED or STALLED. Ships cs-claude-code-rollout agent, /cs-claude-rollout and /cs-claude-settings-lint commands, 3 references, a baseline managed-settings policy and a four-phase rollout plan.
SOC2, HIPAA, and GDPR compliance validation, secrets scanning, compliance checklists, and regulatory documentation
Detects insecure default configurations including hardcoded credentials, fallback secrets, weak authentication defaults, and dangerous values in production
Manage environment configurations and secrets across deployments
Scan codebase for exposed secrets, API keys, passwords, and sensitive credentials
Integrate with secrets managers (Vault, AWS Secrets Manager, etc)
