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-checkgit 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)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.version-check"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.version-check.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.01194 |
| Opus 5 | $0.00000 | $0.00597 |
| Sonnet 5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
acp.version-check 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 4d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: version-check
🤖 Agent Directive: If you are reading this file, the command
@acp-version-checkhas 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.sh
Purpose: Display current ACP version and compatibility information Category: Maintenance Frequency: As Needed
What This Command Does
This command displays the current version of ACP installed in the project by running a simple script that extracts version information from AGENT.md. It provides a quick way to check which version you're using without needing to manually open files.
Use this command when you need to verify your ACP version, check compatibility with other tools, or before reporting issues. It's a simple, read-only operation that provides version information at a glance.
Unlike @acp-version-check-for-updates which checks for newer versions, this command only shows your current version without making any network requests.
Prerequisites
- ACP installed in project (AGENT.md exists)
-
agent/scripts/acp.version-check.shexists (or can extract from AGENT.md directly)
Steps
1. Run Version Script
Execute the version check script.
Actions:
- Run
./agent/scripts/acp.version-check.sh - Script extracts version from AGENT.md using grep
- Displays version, created date, and status
Expected Outcome: Version information displayed
Alternative (if script doesn't exist):
# Extract version directly from AGENT.md
grep -m 1 "^\*\*Version\*\*:" AGENT.md | sed 's/.*: //'
Verification
- Version script executed successfully (or AGENT.md read directly)
- Version number displayed
- Output is clear and well-formatted
- No errors encountered
Expected Output
Files Modified
None - this is a read-only command
Console Output
📦 ACP Version Information
Version: 1.0.3
Created: 2026-02-11
Status: Production Pattern
✓ ACP is installed
To check for updates: ./agent/scripts/acp.version-check-for-updates.sh
To update ACP: ./agent/scripts/acp.version-update.sh
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.
- 4d ago First seen · 192 lines · 0 tokens per session scan A 7a764fd87309
acp.version-check 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,194 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.
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.