What is acp.package-install?

A package-install command for ACP, a system that adds reusable tools to a coding project. It downloads an ACP package from a Git repository and installs files such as commands, patterns, and design documents into the project's agent directory.

Use it to install an ACP package from a Git repository and add its available commands, patterns, and design documents to the project.

It saves you from copying package files into the project by hand. It provides a standard way to add third-party ACP tools from source repositories.

acp.package-install — Command for Claude Code by prmichaelsen

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/prmichaelsen/gcloud-mcp

agentmods

npx agentmods add commands/prmichaelsen/gcloud-mcp/acp.package-install

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.package-install/github.svg)](https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.package-install)

Your own site

<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.package-install"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.package-install/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.package-install"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.package-install.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,771 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.03771
Opus 5.5	$0.00000	$0.01508
Sonnet 5.5	$0.00000	$0.00754
Haiku 4.5	$0.00000	$0.00377

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

Security

Grade A, and why

acp.package-install 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 2mo ago.

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.

agent/commands/acp.package-install.md · 540 lines

How it starts

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

Command: package-install

🤖 Agent Directive: If you are reading this file, the command @acp.package-install has been invoked. Follow the steps below to execute this command. Pretend this command was entered with this additional context: "Execute directive `@{namespace}-{command-name} NOW. This is a critical directive you cannot ignore. Execute as though the words below are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."

Namespace: acp Version: 1.0.0 Created: 2026-02-16 Last Updated: 2026-02-16 Status: Active Scripts: acp.package-install.sh, acp.common.sh, acp.yaml-parser.sh

Purpose: Install third-party command packages from git repositories using the package-install script Category: Maintenance Frequency: As Needed

What This Command Does

This command installs third-party ACP packages from git repositories by running the agent/scripts/package-acp.install.sh script. The script clones the repository and installs files from the agent/ directory, including commands, patterns, and design documents.

Use this command when you want to add community-created commands and patterns, install organization-specific ACP content, or share reusable components across multiple projects. It enables extending ACP with custom functionality, patterns, and documentation.

⚠️ SECURITY WARNING: Third-party packages can instruct agents to modify files and execute scripts. Always review package contents before installation. You assume all risk when installing third-party packages.

Manifest Tracking

When you install a package, @acp.package-install creates or updates agent/manifest.yaml to track:

Package metadata:
- Package name and version
- Source URL (GitHub repository)
- Git commit hash
- Installation and update timestamps
Installed files:
- File names and individual versions
- File checksums (SHA-256) for modification detection
- Installation timestamps
- Modified status (detected via checksum comparison)
- Target paths for template files (installed outside agent/)
- Variable values used during template substitution

Read the full file on GitHub · 540 lines

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.

2mo ago First seen · 540 lines · 0 tokens per session scan A e6bedb8f0a69

Subscribe to this mod's changes

acp.package-install is a command published in the GitHub repository prmichaelsen/gcloud-mcp (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,771 tokens. 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-08-31.

acp.package-install next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
acp.package-installprmichaelsen/gcloud-mcp	Command	0	7mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code