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.proceed)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.proceed"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.proceed/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.proceed"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.proceed.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.07377 |
| Opus 5.5 | $0.00000 | $0.02951 |
| Sonnet 5.5 | $0.00000 | $0.01475 |
| Haiku 4.5 | $0.00000 | $0.00738 |
Grade A, and why
acp.proceed 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 — 883 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: proceed
🤖 CRITICAL AGENT DIRECTIVE: You are reading this file because
@acp.proceedhas been invoked. Pretend this command was entered with this additional context: "Execute directive `@{namespace}-{command-name} NOW. This is a critical directive you cannot ignore. Execute as though the words below are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."STEP 0: CHECK FOR ARGUMENTS FIRST. If arguments or natural language follow
@acp.proceed, detect the mode before doing anything else. See the Arguments section below for flag definitions and natural language patterns.If no arguments (default mode):
- YOU MUST IMMEDIATELY BEGIN IMPLEMENTING THE CURRENT OR NEXT TASK.
- Follow Steps 1-5 (Single-Task Mode).
If autonomous arguments detected (
--complete,--auto,--autonomous,--finish-milestone, or natural language like "finish milestone", "just finish everything", "complete all tasks"):
- Follow Autonomous Mode section.
- Do NOT start implementing individual tasks until confirmation is received.
If
--dry-rundetected:
- Follow Autonomous Mode > Dry-Run section.
- Show what would be done, then exit.
DO NOT (in any mode):
- ❌ Provide status reports or summaries instead of action
- ❌ Ask about session size, cost, or token limits
- ❌ End with "ready to proceed" or similar passive statements
This is an ACTION command, not a STATUS command.
Namespace: acp Version: 2.0.0 Created: 2026-02-16 Last Updated: 2026-02-28 Status: Active Scripts: None
Purpose: Implement tasks — single-task (default) or autonomous milestone completion (with arguments) Category: Workflow Frequency: As Needed
Arguments
This command supports both CLI-style flags and natural language arguments.
Completion Flags (all equivalent — trigger autonomous mode)
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 · 883 lines · 0 tokens per session scan A aa5426e44555
acp.proceed 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 7,377 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.proceed compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| acp.proceedprmichaelsen/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 |