Jacobpevans Claude Code Plugins
JacobPEvans Claude Code Plugins is a Claude Code plugin marketplace for the Build phase that bundles seventeen hook-driven guardrails, validators, and infra helpers for disciplined agent sessions.
by JacobPEvans · github.com/JacobPEvans/claude-code-plugins
Install a 17-plugin Claude Code bundle when stock marketplaces lack git guards, hook validators, infra helpers, and repo hygiene you want enforced on every session.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install jacobpevans-claude-code-plugins@JacobPEvans/claude-code-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:JacobPEvans/claude-code-plugins") and the paste-ready config with skillselion.get_install_config("plugin:JacobPEvans/claude-code-plugins").
What it does
JacobPEvans Claude Code Plugins is a personal plugin registry for builders who already use Claude Code daily but found generic marketplaces thin on opinionated guardrails. The collection bundles roughly seventeen plugins that sit on hooks and agent configuration rather than replacing your app code: git and main-branch guards, markdown and token validation, WebFetch limits, issue and merge hygiene, and infra-adjacent helpers for Terraform, Ansible, Proxmox, and secrets via Doppler. Solo and indie developers shipping with agents benefit when they want consistent enforcement—always-allow patterns, pretool checks, and delegation scripts—without maintaining each rule by hand in every repo. It is intermediate complexity because you must understand Claude Code plugin layout, hook triggers, and which plugins to enable per project. Use it during Build when wiring agent tooling, during Ship when you need review and security gates, and during Operate when telemetry, Splunk-style lookup, and repo cleanup matter. It is a curated plugin marketplace for Claude Code, not a single skill file or an MCP server catalog.
Highlights
- 17-plugin bundle covering git permission guards, branch protection, markdown and token validators, and WebFetch hygiene
- Infrastructure and ops-oriented plugins for Terraform, Ansible, Proxmox, Doppler secrets, and Splunk-oriented troublesho
- GitHub Actions and cross-repo orchestration patterns for pipelines, issue linking, and multi-repo maintenance
- Session lifecycle hooks (session start, user prompt submit) plus research-first and native-tool-first methodology enforc
- Quality and security posture: CodeQL-oriented analysis, permission guards, and systematic review/delegation workflows
Why builders use it
Stock Claude Code marketplaces rarely combine git guards, session hooks, markdown validation, and infra-specific plugins in one place you trust for daily shipping.
After you register the marketplace and enable the plugins you need, Claude Code sessions inherit consistent permissions, validation, and delegation patterns across repos without re-scouring the web each time.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 2 stars, 0 votes.
FAQ
Who is jacobpevans-claude-code-plugins for?
It is for Claude Code users who maintain serious codebases and want JacobPEvans’s custom plugins—git guards, validators, infra helpers, and session hooks—in one installable bundle.
When should I use jacobpevans-claude-code-plugins?
Use it when you are wiring agent tooling during Build, tightening review and security during Ship, or standardizing session behavior during Operate and have not found equivalent quality in default marketplaces.
How do I add jacobpevans-claude-code-plugins to my agent?
Add the JacobPEvans/claude-code-plugins repository as a Claude Code plugin marketplace source, then enable individual plugins from the bundle in your project or user Claude Code plugin configuration.
Comments
Share how you use jacobpevans-claude-code-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.