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.
git 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-check-for-updates)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.version-check-for-updates"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.version-check-for-updates/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.
<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.version-check-for-updates"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.version-check-for-updates.svg" alt="Reviewed on agentmods" width="80" 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.01685 |
| Opus 5.5 | $0.00000 | $0.00674 |
| Sonnet 5.5 | $0.00000 | $0.00337 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
acp.version-check-for-updates 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.
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: version-check-for-updates
🤖 Agent Directive: If you are reading this file, the command
@acp-version-check-for-updateshas 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-check-for-updates.sh
Purpose: Check if newer version of ACP is available without applying updates Category: Maintenance Frequency: Per Session
What This Command Does
This command checks if a newer version of ACP is available by running the update check script. It's a non-destructive operation that only reports whether updates exist and what changed, without modifying any files.
Use this command at the start of sessions (it's part of @acp-init) or when you want to see if improvements are available. It shows what's new via the CHANGELOG and lets you decide whether to update.
Unlike @acp-version-update which applies updates immediately, this command only checks and reports, giving you control over when to update.
Prerequisites
- ACP installed in project
-
agent/scripts/acp.version-check-for-updates.shexists - Internet connection available
- Git installed
Steps
1. Run Update Check Script
Execute the check-for-updates script.
Actions:
- Check if
./agent/scripts/acp.version-check-for-updates.shexists - If exists, run the script
- If doesn't exist, report that update checking is unavailable
- Capture script output
Expected Outcome: Update status determined
2. Parse Script Output
Interpret the results from the update check.
Actions:
- Check if updates are available
- Extract available version number (if updates exist)
- Note if already up to date
- Handle any errors from script
Expected Outcome: Update status understood
3. Display Update Status
Show whether updates are available.
Actions:
- If up to date: Display success message
- If updates available: Show new version number
- Display current version for comparison
- Show update availability clearly
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 · 277 lines · 0 tokens per session scan A 6418fef781d7
acp.version-check-for-updates 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 1,685 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.version-check-for-updates compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| acp.version-check-for-updatesprmichaelsen/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 |