plugin-prompt-injection-reuse

Standardize plugin prompt injection via existing registries and lifecycle flows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/liuyu520/cc_source --skill plugin-prompt-injection-reuse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-prompt-injection-reuse
Source: https://github.com/liuyu520/cc_source/tree/main/.claude/skills/plugin-prompt-injection-reuse
Command: npx skills add https://github.com/liuyu520/cc_source --skill plugin-prompt-injection-reuse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reuse existing pluginPromptSections registry, systemPromptSection cache wrapper, and plugin enable/disable flows to standardize prompt injection from plugins across builtin and marketplace plugins, ensuring consistent prompts.

Core Features & Use Cases

  • Central registry for plugin prompt sections with deduplication and plugin-scoped names
  • Cached system prompt sections to minimize recomputation and preserve prompt integrity
  • Lifecycle-aware registration: enable registers sections, disable removes them, and refresh clears stale entries for marketplace plugins
  • Dynamic content support for builtin plugins (functions) and static content for marketplace plugins, with safe fallbacks

Quick Start

To begin, register a builtin plugin with systemPromptSections and verify that its sections are registered on enable and removed on disable.

Frequently Asked Questions about plugin-prompt-injection-reuse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize prompt injection across builtin and marketplace plugins?

Standardize prompt injection by reusing the existing pluginPromptSections registry and systemPromptSection cache wrapper to ensure consistent prompts across builtin and marketplace plugins. This approach deduplicates sections and ensures clean cleanup during refresh.

Why do my plugin prompt sections duplicate after refreshing the registry?

Plugin prompt sections duplicate because stale entries persist without lifecycle-aware registration. Implementing a refresh flow that clears stale entries for marketplace plugins ensures deduplicated sections and maintains prompt integrity.

How do I cache system prompt sections to minimize recomputation overhead?

Cache system prompt sections by wrapping them in a systemPromptSection cache layer to minimize recomputation overhead and preserve prompt integrity. This safely handles dynamic content for builtin plugins and static content for marketplace plugins.

Can I use dynamic content functions for marketplace plugin prompt sections?

Dynamic content functions are supported for builtin plugins, while marketplace plugins use static content. The system provides safe fallbacks to maintain prompt integrity if marketplace plugins cannot execute dynamic functions.

What happens to registered prompt sections when a plugin is disabled?

Disabling a plugin removes its registered prompt sections from the central registry. This lifecycle-aware registration ensures that enable registers sections, disable removes them, and refresh clears stale entries.

Does the plugin registry support plugin-scoped names for prompt injection?

The pluginPromptSections registry supports plugin-scoped names to prevent naming collisions and ensure deduplicated sections. This central registry standardizes prompt injection across builtin and marketplace plugins.