plugin-settings

plugin-settings is a skill for Claude Code from anthropics/claude-plugins-official. It costs 81 tokens per session (3,113 once invoked), scanned B, original, Apache-2.0.

A configuration pattern for storing per-project plugin settings and state in a local Markdown file with YAML fields at the top.

In plain words
What is it for?
It is for defining user-editable options, prompts, notes, and state that hooks, commands, and agents can read.
Why use it?
It lets plugin behavior vary by project without putting personal settings or session state into version control.

Skill for Claude Code ✓ vendor

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the plugin-dev plugin — 7 skills, 1 command, 3 agents shipped together

Good fit It is for defining user-editable options, prompts, notes, and state that hooks, commands, and agents can read.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anthropics/claude-plugins-official/plugin-settings
About the project

Claude Code Plugins Directory is a marketplace containing plugins for Claude Code, including tools, commands, skills, agents, hooks, and model context servers. Claude Code users browse it to install Anthropic-maintained or approved third-party extensions.

anthropics/claude-plugins-official · 42,673 stars · on GitHub · code.claude.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add anthropics/claude-plugins-official --skill plugin-settings
Clone the repo
git clone --depth 1 https://github.com/anthropics/claude-plugins-official

Made for: Claude Code.

Or install plugin-dev, the plugin that ships this one along with the rest of its 7 skills, 1 command, 3 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plugin-settings

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthropics/claude-plugins-official/plugin-settings/github.svg)](https://agentmods.dev/skills/anthropics/claude-plugins-official/plugin-settings)
Your own site
<a href="https://agentmods.dev/skills/anthropics/claude-plugins-official/plugin-settings"><img src="https://agentmods.dev/badge/skills/anthropics/claude-plugins-official/plugin-settings/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plugin-settings

Your own site · 80×15
<a href="https://agentmods.dev/skills/anthropics/claude-plugins-official/plugin-settings"><img src="https://agentmods.dev/badge/skills/anthropics/claude-plugins-official/plugin-settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,113 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 14 Sept 2026
  • Snyk pass 14 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Privilege Escalation · line 420
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.03113
Opus 5.5 $0.00032 $0.01245
Sonnet 5.5 $0.00016 $0.00623
Haiku 4.5 $0.00008 $0.00311

Measured 1mo ago against content hash 028b955244b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

plugin-settings scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

The scan reads SKILL.md. This mod also ships 3 executable files (examples/read-settings-hook.sh, scripts/parse-frontmatter.sh, scripts/validate-settings.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Readable by user only (`chmod 600`)
Origin

Copies of this mod

8 near-identical copies found in the catalogue:

plugins/plugin-dev/skills/plugin-settings/SKILL.md · 545 lines

How it starts

The opening of the file, as written. The whole thing — 545 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plugin Settings Pattern for Claude Code Plugins

Overview

Plugins can store user-configurable settings and state in .claude/plugin-name.local.md files within the project directory. This pattern uses YAML frontmatter for structured configuration and markdown content for prompts or additional context.

Key characteristics:

  • File location: .claude/plugin-name.local.md in project root
  • Structure: YAML frontmatter + markdown body
  • Purpose: Per-project plugin configuration and state
  • Usage: Read from hooks, commands, and agents
  • Lifecycle: User-managed (not in git, should be in .gitignore)

File Structure

Basic Template

---
enabled: true
setting1: value1
setting2: value2
numeric_setting: 42
list_setting: ["item1", "item2"]
---

# Additional Context

This markdown body can contain:
- Task descriptions
- Additional instructions
- Prompts to feed back to Claude
- Documentation or notes

Example: Plugin State File

.claude/my-plugin.local.md:

---
enabled: true
strict_mode: false
max_retries: 3
notification_level: info
coordinator_session: team-leader
---

# Plugin Configuration

This plugin is configured for standard validation mode.
Contact @team-lead with questions.

Reading Settings Files

From Hooks (Bash Scripts)

Pattern: Check existence and parse frontmatter

#!/bin/bash
set -euo pipefail

# Define state file path
STATE_FILE=".claude/my-plugin.local.md"

# Quick exit if file doesn't exist
if [[ ! -f "$STATE_FILE" ]]; then
  exit 0  # Plugin not configured, skip
fi

# Parse YAML frontmatter (between --- markers)
FRONTMATTER=$(sed -n '/^---$/,/^---$/{ /^---$/d; p; }' "$STATE_FILE")

# Extract individual fields
ENABLED=$(echo "$FRONTMATTER" | grep '^enabled:' | sed 's/enabled: *//' | sed 's/^"\(.*\)"$/\1/')
STRICT_MODE=$(echo "$FRONTMATTER" | grep '^strict_mode:' | sed 's/strict_mode: *//' | sed 's/^"\(.*\)"$/\1/')

# Check if enabled
if [[ "$ENABLED" != "true" ]]; then
  exit 0  # Disabled
fi

# Use configuration in hook logic
if [[ "$STRICT_MODE" == "true" ]]; then
  # Apply strict validation
  # ...
fi

Read the full file on GitHub · 545 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 545 lines · 81 tokens per session scan B 028b955244b9

Subscribe to this mod's changes

plugin-settings is a skill published in the GitHub repository anthropics/claude-plugins-official (42,673 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 3,113 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

feature-prioritisation

Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…

mohitagw15856/pm-claude-skills · 103 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

factory-human-digest

Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.

BuilderIO/skills · 41 tokens

factory

Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.

BuilderIO/skills · 32 tokens

factory-collect

Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.

BuilderIO/skills · 41 tokens

factory-recover

Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.

BuilderIO/skills · 26 tokens