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.version-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.version-update)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.version-update"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.version-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 | $0.00000 | $0.01896 |
| Opus 5 | $0.00000 | $0.00948 |
| Sonnet 5 | $0.00000 | $0.00379 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
acp.version-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 2d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: version-update
🤖 Agent Directive: If you are reading this file, the command
@acp-version-updatehas been invoked. Follow the steps below to execute this command.
Namespace: acp Version: 1.0.0 Created: 2026-02-16 Last Updated: 2026-02-16 Status: Active Scripts: acp.version-update.sh, acp.common.sh
Purpose: Update ACP files (AGENT.md, templates, scripts) to the latest version Category: Maintenance Frequency: When Updates Available
What This Command Does
This command updates your ACP installation to the latest version by running the update script. It downloads the latest AGENT.md, template files, and utility scripts from the ACP repository, replacing your current versions while preserving your project-specific files.
Use this command when @acp-version-check-for-updates reports that updates are available, or when you want to get the latest ACP improvements. The update process is git-friendly and reversible.
Unlike @acp-version-check-for-updates which only checks, this command actually applies the updates. It's recommended to commit your changes before updating so you can revert if needed.
Prerequisites
- ACP installed in project
-
agent/scripts/acp.version-update.shexists - Internet connection available
- Git repository initialized (recommended for easy rollback)
- Changes committed (recommended)
Steps
1. Verify Prerequisites
Check that update can proceed safely.
Actions:
- Verify
./agent/scripts/acp.version-update.shexists - Check internet connection
- Recommend committing changes if git repo exists
- Warn user that files will be updated
Expected Outcome: Prerequisites confirmed or user warned
2. Run Update Script
Execute the update script.
Actions:
- Run
./agent/scripts/acp.version-update.sh - Script will:
- Clone latest ACP repository
- Update AGENT.md
- Update all template files
- Update utility scripts
- Preserve your project files (non-templates)
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.
- 2d ago First seen · 290 lines · 0 tokens per session scan A 20f6f9815eea
acp.version-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 1,896 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
git
Git operations with intelligent commit messages and workflow optimization.
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.