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.
git clone --depth 1 https://github.com/prmichaelsen/gcloud-mcpnpx agentmods add commands/prmichaelsen/gcloud-mcp/acp.package-listWrote 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.
[](https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.package-list)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.package-list"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.package-list.svg" alt="Measured on agentmods" height="20"></a>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.01821 |
| Opus 5 | $0.00000 | $0.00911 |
| Sonnet 5 | $0.00000 | $0.00364 |
| Haiku 4.5 | $0.00000 | $0.00182 |
Grade A, and why
acp.package-list 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: package-list
🤖 Agent Directive: If you are reading this file, the command
@acp.package-listhas been invoked. Follow the steps below to execute this command.
Namespace: acp Version: 1.0.0 Created: 2026-02-18 Last Updated: 2026-02-18 Status: Active Scripts: acp.package-list.sh, acp.common.sh, acp.yaml-parser.sh
Purpose: List installed ACP packages with versions, file counts, and optional details Category: Information Frequency: As Needed
What This Command Does
This command displays all installed ACP packages by reading agent/manifest.yaml (local) or ~/.acp/manifest.yaml (global) and showing package names, versions, and file counts. It provides optional verbose mode for detailed information and filters for outdated or modified packages.
Use this command when you want to see what packages are installed locally or globally, check package versions, identify packages with updates available, or find packages with local modifications.
Auto-Initialization
When using the --global flag for the first time, the system automatically initializes ~/.acp/ infrastructure:
- Creates
~/.acp/directory - Installs full ACP (templates, scripts, schemas)
- Creates
~/.acp/projects/directory - Creates
~/.acp/agent/manifest.yamlfor package tracking
This happens automatically - no manual setup required.
Prerequisites
- ACP installed in project
-
agent/manifest.yamlexists (packages have been installed) -
agent/scripts/acp.package-list.shexists
Steps
1. Run Package List Script
Execute the list script with desired options.
Actions:
- Run
./agent/scripts/acp.package-list.shwith optional flags:# Basic list (local packages) ./agent/scripts/acp.package-list.sh # List global packages ./agent/scripts/acp.package-list.sh --global # Verbose mode (detailed information) ./agent/scripts/acp.package-list.sh --verbose # Show only outdated packages ./agent/scripts/acp.package-list.sh --outdated # Show only packages with local modifications ./agent/scripts/acp.package-list.sh --modified # Combine flags ./agent/scripts/acp.package-list.sh --global --verbose
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.
- 6d ago First seen · 281 lines · 0 tokens per session scan A af3e62b610b6
acp.package-list is a command published in the GitHub repository prmichaelsen/gcloud-mcp (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,821 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.