Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/prmichaelsen/gcloud-mcp/acp.package-updategit clone --depth 1 https://github.com/prmichaelsen/gcloud-mcpWrote 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-update)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.package-update"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.package-update.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.02388 |
| Opus 5 | $0.00000 | $0.01194 |
| Sonnet 5 | $0.00000 | $0.00478 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade A, and why
acp.package-update 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 5d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: package-update
🤖 Agent Directive: If you are reading this file, the command
@acp.package-updatehas 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-update.sh, acp.common.sh, acp.yaml-parser.sh
Purpose: Update installed ACP packages to their latest versions with smart conflict detection Category: Maintenance Frequency: As Needed
What This Command Does
This command updates installed ACP packages to their latest versions by comparing the current version in agent/manifest.yaml with the latest version in the package repository. It intelligently detects locally modified files via checksum comparison and provides conflict resolution options.
Use this command when you want to get the latest bug fixes, features, and improvements from installed packages. The command can update all packages at once or specific packages individually, and it respects local modifications to prevent accidental overwrites.
Unlike @acp.version-update which updates ACP itself, this command updates third-party packages installed via @acp.package-install.
Prerequisites
- ACP installed in project
-
agent/manifest.yamlexists with installed packages - Git installed and available
- Internet connection available
-
agent/scripts/acp.package-update.shexists
Steps
1. Choose Update Mode
Decide what to update.
Update Modes:
A. Check for Updates (preview only):
./agent/scripts/acp.package-update.sh --check
Shows available updates without installing them.
B. Update All Packages:
./agent/scripts/acp.package-update.sh
Updates all installed packages to latest versions.
C. Update Specific Package:
./agent/scripts/acp.package-update.sh <package-name>
Updates only the specified package.
D. Update with Options:
# Skip modified files automatically
./agent/scripts/acp.package-update.sh --skip-modified
# Force overwrite modified files
./agent/scripts/acp.package-update.sh --force
# Auto-confirm (no prompts)
./agent/scripts/acp.package-update.sh -y
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.
- 5d ago First seen · 362 lines · 0 tokens per session scan A f2fa4aa4f5e3
acp.package-update 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 2,388 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.