edit-plugin

edit-plugin is a skill for Claude Code from digital-stoic-org/agent-skills. It costs 61 tokens per session (849 once invoked), scanned A, original, MIT.

A release-management tool for updating plugin versions and related release metadata.

In plain words
What is it for?
Use it when adding, removing, or changing skills and commands, or when preparing a plugin release.
Why use it?
It reduces the manual work involved in keeping a plugin's version information aligned with its changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions .claude-plugin; names the AskUserQuestion tool.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/mat/dev/agent-skills/.

Part of the toolsmith plugin — 5 skills shipped together

Good fit Use it when adding, removing, or changing skills and commands, or when preparing a plugin release.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add digital-stoic-org/agent-skills
Claude Code
/plugin install toolsmith

Made for: Claude Code.

Or install toolsmith, the plugin that ships this one along with the rest of its 5 skills.

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 edit-plugin

README.md
[![agentmods](https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/edit-plugin/github.svg)](https://agentmods.dev/skills/digital-stoic-org/agent-skills/edit-plugin)
Your own site
<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/edit-plugin"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/edit-plugin/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 edit-plugin

Your own site · 80×15
<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/edit-plugin"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/edit-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 849 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00061 $0.00849
Opus 5.5 $0.00024 $0.00340
Sonnet 5.5 $0.00012 $0.00170
Haiku 4.5 $0.00006 $0.00085

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

Security

Grade A, and why

edit-plugin scanned grade A with 0 findings 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 2 executable files (scripts/bump-version.sh, scripts/detect-changes.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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

toolsmith/skills/edit-plugin/SKILL.md · 83 lines

How it starts

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

Edit Plugin

Resolve → Detect → Version → Update → Review

⚠️ AskUserQuestion Guard

CRITICAL: After EVERY AskUserQuestion call, check if answers are empty/blank. Known Claude Code bug: outside Plan Mode, AskUserQuestion silently returns empty answers without showing UI.

If answers are empty: DO NOT proceed with assumptions. Instead:

  1. Output: "⚠️ Questions didn't display (known Claude Code bug outside Plan Mode)."
  2. Present the options as a numbered text list and ask user to reply with their choice number.
  3. WAIT for user reply before continuing.

0. Resolve Plugin

Determine PLUGIN_DIR (relative to repo root, e.g. dstoic, biz, gtd):

  1. From $ARGUMENTS: If first arg matches a dir with .claude-plugin/plugin.json → use it
  2. From cwd: Walk up from cwd, find nearest .claude-plugin/plugin.json → derive plugin name from parent dir
  3. Ambiguous/not found: AskUserQuestion listing discovered plugins (dirs containing .claude-plugin/plugin.json)

Read current version from ${PLUGIN_DIR}/.claude-plugin/plugin.json.

1. Detect Changes

${CLAUDE_PLUGIN_ROOT}/skills/edit-plugin/scripts/detect-changes.sh <repo-root> <plugin-dir>

If no changes detected, ask user what to include.

2. Version Bump

Auto-detect from changes:

  • minor: new skill/command added, breaking changes
  • patch: updates, bug fixes, doc changes

User override via $ARGUMENTS (e.g., biz minor "Add ux-strategize").

${CLAUDE_PLUGIN_ROOT}/skills/edit-plugin/scripts/bump-version.sh <current-version> <patch|minor>

3. Update Version (all files)

Atomic — never partially update. Two tiers:

Required: ${PLUGIN_DIR}/.claude-plugin/plugin.json — always update.

Discovered: Grep repo root for old version string. Filter results:

  • Include: files within ${PLUGIN_DIR}/ + repo-root metadata files referencing this plugin
  • Exclude: .git/, this skill's SKILL.md, this skill's reference.md
  • marketplace.json: Only update plugins[name=${PLUGIN_DIR}].version entry. Update metadata.version only if this plugin is the primary (currently dstoic).

Read the full file on GitHub · 83 lines

Files

What ships with it

3 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 · 83 lines · 61 tokens per session scan A 9f502e4db9b7

Subscribe to this mod's changes

edit-plugin is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 12d ago), licensed MIT. It adds 61 tokens to every session and 849 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens