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.resume)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.resume"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.resume/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.resume"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.resume.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.01519 |
| Opus 5 | $0.00000 | $0.00759 |
| Sonnet 5 | $0.00000 | $0.00304 |
| Haiku 4.5 | $0.00000 | $0.00152 |
Grade A, and why
acp.resume 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 8d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: resume
🤖 Agent Directive: If you are reading this file, the command
@acp.resumehas been invoked. Follow the steps below to execute this command. 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."
Namespace: acp Version: 1.0.0 Created: 2026-02-21 Last Updated: 2026-02-21 Status: Active Scripts: None
Purpose: Resume work on a project by initializing context, reviewing recent progress, and continuing with the next task Category: Workflow Frequency: Per Session
What This Command Does
This command is a convenient alias that combines three essential workflow commands into one:
- Initialize Context - Loads all project documentation via
@acp.init - Review Recent Work - Reads the latest session report to understand what was done
- Continue Work - Proceeds with the current/next task via
@acp.proceed
Use this when: Starting a new session or returning to a project after a break.
Prerequisites
- ACP installed in project
-
agent/progress.yamlexists - Session reports exist in
agent/reports/(optional but recommended)
Steps
1. Initialize Agent Context
Run the initialization workflow to load complete project context.
Actions:
- Execute
@acp.initworkflow - Check for ACP updates
- Read all agent documentation
- Read key files from
agent/index/(via@acp.initstep 2.8) - Review key source files
- Update stale documentation
- Refresh progress tracking
Expected Outcome: Complete project context loaded (including key file index)
2. Read Latest Session Report
Find and read the most recent session report to understand what was accomplished.
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.
- 8d ago First seen · 240 lines · 0 tokens per session scan A 735068161e7c
acp.resume 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,519 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.