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-infoWrote 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-info)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.package-info"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.package-info.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.01373 |
| Opus 5 | $0.00000 | $0.00687 |
| Sonnet 5 | $0.00000 | $0.00275 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
acp.package-info 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 7d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: package-info
🤖 Agent Directive: If you are reading this file, the command
@acp.package-infohas been invoked. Follow the steps below to execute this command.
Namespace: acp Version: 2.0.0 Created: 2026-02-18 Last Updated: 2026-02-22 Status: Active Scripts: acp.package-info.sh, acp.common.sh, acp.yaml-parser.sh
Purpose: Display detailed information about a specific installed package (local or global) Category: Information Frequency: As Needed
What This Command Does
This command shows comprehensive information about an installed ACP package, including metadata (source, version, commit, location), all installed files with their versions, and modification status for each file. Supports both local packages (./agent/) and global packages (~/.acp/packages/).
Use this command when you need detailed information about a package (local or global), want to see which files are installed, check for local modifications, or verify package metadata before updating or removing.
Prerequisites
- ACP installed in project
-
agent/manifest.yamlexists with installed packages -
agent/scripts/acp.package-info.shexists - Package name is known (use
@acp.package-listto see installed packages)
Steps
1. Run Package Info Script
Execute the info script with the package name.
Actions:
- Run
./agent/scripts/acp.package-info.sh [--global] <package-name> - Script will display all package information
- Use
--globalflag to show global package info
Examples:
# Show local package info
./agent/scripts/acp.package-info.sh firebase
# Show global package info
./agent/scripts/acp.package-info.sh --global firebase
Expected Outcome: Detailed package information displayed
2. Review Package Information
Analyze the displayed information.
Actions:
- Note package version and source
- Review installed files list
- Check for modified files (marked with [MODIFIED])
- Verify file versions
- Note commit hash for reference
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.
- 7d ago First seen · 213 lines · 0 tokens per session scan A 9fa5102ab135
acp.package-info 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,373 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.