agentleFS
Sign inStart free
agentic-control-planeagentic-control-plane/claude-code-acp-plugin/skills/acp-upgrade/SKILL.md

acp-upgrade

Skill1 starsChanged 22 days agoMITView on GitHub

Upgrade the ACP governance plugin and hook to the latest version via the canonical installer (human-approved)

  • Pipes a download into a shell

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this when ACP reports that a newer plugin version is available (an [ACP] upgrade notice at session start), or when the user asks to …

    line 9
  2. Very specific:

    If ACP runs as the Claude Code plugin (the normal case — claude plugin list shows agentic-control-plane@acp), the only command that …

    line 23
  3. Very specific:

    If ACP runs as a standalone hook (~/.acp/govern.mjs wired directly in ~/.claude/settings.json, no plugin listed), run the canonical …

    line 35
  4. Distinctive:

    Do not modify the command, add flags, or chain other commands onto it: only the exact canonical form is recognized.

    line 47
  5. Very specific:

    Never edit ~/.acp/govern.mjs, ~/.claude/settings.json hooks, or the plugin files directly — governance machinery is human-only.

    line 61
  6. Distinctive:

    Never work around a denied installer run — the approval link in the deny reason is the path forward.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ACP upgrade

Use this when ACP reports that a newer plugin version is available (an [ACP] upgrade notice at session start), or when the user asks to upgrade ACP.

Why upgrades matter

The govern hook is the enforcement point on this machine. Old versions can carry enforcement gaps — for example, pre-0.11.0 hooks could time out under gateway latency, and a timed-out PreToolUse hook is non-blocking: the call runs even though the server issued a deny. Upgrading closes gaps that are already fixed upstream.

How to upgrade

  1. If ACP runs as the Claude Code plugin (the normal case — claude plugin list shows agentic-control-plane@acp), the only command that switches the active version is:

    claude plugin update agentic-control-plane@acp

    Re-running the installer does NOT upgrade an installed plugin (claude plugin install is a no-op on one that is already installed — acp-install#64), so do not send the user back to the installer for this.

    If ACP runs as a standalone hook (~/.acp/govern.mjs wired directly in ~/.claude/settings.json, no plugin listed), run the canonical installer, exactly:

    curl -sf https://agenticcontrolplane.com/install.sh | bash

    Expect an approval requirement: refreshing the governance hook is step_up-gated at unattended tiers, and the deny reason carries the approval link. Ask your human to approve it in the ACP console, then run the SAME command again — the consumed approval lets it through. Do not modify the command, add flags, or chain other commands onto it: only the exact canonical form is recognized.

  2. Either way, tell the user to restart Claude Code (the running session keeps the old hook in memory).
  3. On the next session start the hook re-attests: the console session view shows the new version and hash. If the badge still shows the old version, the update did not take — claude plugin list should show the version in ~/.claude/plugins/marketplaces/acp/.claude-plugin/marketplace.json (plugin), or ~/.acp/govern.mjs should have been rewritten (standalone).

Never

  • Never edit ~/.acp/govern.mjs, ~/.claude/settings.json hooks, or the plugin files directly — governance machinery is human-only; the canonical installer behind a human approval is the ONE sanctioned path.
  • Never work around a denied installer run — the approval link in the deny reason is the path forward.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free