Overrides
- Updated July 20, 2026
- snjnlsn/snjnlsn-marketplace
Overrides is an agent skill that lets you customize and hook into other Claude Code plugins via a personal overrides plugin.
About
Overrides is a thin marketplace plugin skill for Claude Code users who run the snjnlsn-marketplace layout and need a dedicated place to customize third-party plugins without merging changes upstream. developers treating the agent as their primary dev environment install it during Build when they are wiring hooks, command tweaks, or behavioral patches that should survive marketplace updates. The published README only states that it personalizes and hooks into other plugins; expect SKILL.md or plugin sources in-repo to list exact override entry points. It is not a general-purpose app integration—it's infrastructure for your agent toolchain. Confidence is moderate because Prism ingested sparse metadata; verify hook contracts in the repository before relying on them in production workflows. Use when you already depend on Claude Code plugins and want a sanctioned override directory rather than ad-hoc edits inside node_modules or cached plugin trees.
- Personal plugin overrides that patch or extend behavior of other Claude Code plugins
- Hooks into the snjnlsn-marketplace plugin layout under ./plugins/overrides
- Keeps customizations local instead of editing vendored marketplace sources
- Intended for power users maintaining a private marketplace fork or overlay
- Pairs with sibling local_conf for environment-specific agent settings
Overrides by the numbers
- Data as of Jul 21, 2026 (Skillselion catalog sync)
/plugin marketplace add snjnlsn/snjnlsn-marketplace/plugin install overrides@snjnlsn-marketplaceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | July 20, 2026 |
|---|---|
| Repository | snjnlsn/snjnlsn-marketplace ↗ |
What it does
Layer personal hooks and customizations on top of other Claude Code marketplace plugins without forking upstream packages.
Who is it for?
Best when you're running snjnlsn-marketplace (or similar) and already use multiple Claude Code plugins and want a stable override layer.
Skip if: Skip if you only use stock Claude Code without custom marketplaces, or teams that need cross-IDE MCP integrations instead of plugin overrides.
When should I use this skill?
When you are configuring or extending Claude Code plugins via the snjnlsn-marketplace overrides plugin (personal hooks and customizations).
What you get
You maintain override hooks in a named plugin slot so customizations stay traceable in git and separable from marketplace updates.
- Versioned override definitions that hook into target plugins
- Documented local customization layer separate from upstream plugin sources
Files
Personal plugin overrides — customizes and hooks into other Claude Code plugins.
overrides
Source: ./plugins/overrides
{ "name": "overrides", "source": "./plugins/overrides", "description": "Personal plugin overrides — customizes and hooks into other Claude Code plugins." }
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
A local plugin overlay pattern, not a standalone MCP server or a hosted CI workflow.
FAQ
Who is overrides for?
It is for Claude Code power users maintaining a personal marketplace who need to customize existing plugins without forking every upstream package.
When should I use overrides?
Use it in Build/agent-tooling when you are assembling your agent stack and need durable hooks or patches that apply across your installed plugins.
Is overrides safe to install?
Overrides can change how plugins run locally—check the Security Audits panel on this Prism page and review override code before granting broad filesystem or shell access.